On Fri, Mar 28, 2014 at 12:28:58AM -0700, Andy Zhou wrote: > On Thu, Mar 27, 2014 at 8:29 PM, Ben Pfaff <b...@nicira.com> wrote: > > I don't think it's a good idea to actually exit with an error code, > > because it's a change in behavior that could break scripts. For > > example, I bet that some people use "ovs-vsctl add-port br0 <name>" and > > then separately "ovs-vsctl set interface <name> type=gre options:...". > > Even though it would be better to add and configure in a single command, > > it used to work fine, with exit code 0, to do add in one and configure > > in another, and I wouldn't want to break that if the script checks exit > > status (e.g. with "set -e"). > > I agree with you on being nice to existing scripts. What's is > our answer to (future) scripts that can benefit from such error code? > I suppose we can suggest them to monitor stderr, but not sure if this > is what you had in mind.
I like Thomas's proposal of a "status" command. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
