On Mon, Aug 1, 2016 at 12:49 PM, Ben Pfaff <b...@ovn.org> wrote: > On Mon, Aug 01, 2016 at 12:00:17PM -0500, Ryan Moats wrote: >> When it comes to ovs-appctl, we're looking to set log level access only. >> Since this doesn't really fit into what I think of when I see "--dry-run", >> I'm wondering if this variation of the wrapper concept above >> would do the trick: >> >> #! /bin/sh >> # <code to limit $1 to proper targets> >> # <code to limit $2 to proper log levels> >> exec /real/path/to/ovs-appctl vlog/set "$1:$2" > > Makes sense to me. > > I've also been pondering the difference between --dry-run, which allows > but essentially ignores any command that writes, and some new option we > might invent like --read-only, which would reject with an error any > command that writes. --dry-run might be surprising given that it would > accept silently any command that modifies state.
This I actually agree with, as "--read-only" does make more sense. But if we are the only users, I would be fine with the "--dry-run" option as well. > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
