ovs-ctl: Exit, instead of resuming, after handling fatal signals.
authorBen Pfaff <blp@nicira.com>
Wed, 26 Dec 2012 20:45:34 +0000 (12:45 -0800)
committerBen Pfaff <blp@nicira.com>
Wed, 26 Dec 2012 20:46:28 +0000 (12:46 -0800)
commite044071be06ffd3540f7406dcc73288c733567b4
tree10326caed9e925cfd455db91946727528fad955a
parenta4454ac67c6d38740914d157f73b5083f6912172
ovs-ctl: Exit, instead of resuming, after handling fatal signals.

When I wrote the "trap" calls in ovs-ctl, I had the mistaken notion that
"trap $cmd $signal" would execute $cmd and then exit when $signal was
caught.  This is incorrect.  Instead, it executes $cmd and then resumes
executing the shell script.

On the other hand, "trap $cmd 0" does by itself what I wanted: it causes
the shell to execute $cmd and then exits due to the signal.  So this commit
changes the offending traps to use this form.

Bug #14290.
Signed-off-by: Ben Pfaff <blp@nicira.com>
Acked-by: Kyle Mestery <kmestery@cisco.com>
utilities/ovs-ctl.in