[OpenWrt-Devel] [PATCHv2] [netifd/scripts] make netifd scripts recognize signal strings such as INT/TERM/KILL/... signal in proto_kill_command()

[netifd/scripts] make netifd scripts recognize signal strings such as INT/TERM/KILL/... instead of let the caller do the conversion of symbolic to numeric (e.g. SIGUSR1 -> 16), do the conversion internally - the old mode (numeric) is still supported Signed-off-by: Bastian Bittorf --- scripts/

Re: [OpenWrt-Devel] [PATCHv2] [netifd/scripts] make netifd scripts recognize signal strings such as INT/TERM/KILL/... signal in proto_kill_command()

Am 16.10.2014 14:59 schrieb "Bastian Bittorf" : > > [netifd/scripts] make netifd scripts recognize signal strings such as INT/TERM/KILL/... > > instead of let the caller do the conversion of symbolic to numeric (e.g. SIGUSR1 -> 16), > do the conversion internally - the old mode (numeric) is still s

Re: [OpenWrt-Devel] [PATCHv2] [netifd/scripts] make netifd scripts recognize signal strings such as INT/TERM/KILL/... signal in proto_kill_command()

* Yousong Zhou [18.10.2014 17:58]: > > + signal="$( kill -l "$signal" )" > > the quotes may not work... they work and you should always quote a var, unless you are really sure it is an integer... root@box:~ kill -l "15" TERM root@box:~ kill -l "TERM" 15 bye, bastian _

Re: [OpenWrt-Devel] [PATCHv2] [netifd/scripts] make netifd scripts recognize signal strings such as INT/TERM/KILL/... signal in proto_kill_command()

Am 18.10.2014 23:58 schrieb "Bastian Bittorf" : > > * Yousong Zhou [18.10.2014 17:58]: > > > + signal="$( kill -l "$signal" )" > > > > the quotes may not work... > > they work and you should always quote a var, > unless you are really sure it is an integer... > yes. it's ju