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

2014-10-18 Thread Yousong Zhou
Am 16.10.2014 14:59 schrieb Bastian Bittorf bitt...@bluebottle.com: [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

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

2014-10-18 Thread Bastian Bittorf
* Yousong Zhou yszhou4t...@gmail.com [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,

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

2014-10-18 Thread Yousong Zhou
Am 18.10.2014 23:58 schrieb Bastian Bittorf bitt...@bluebottle.com: * Yousong Zhou yszhou4t...@gmail.com [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

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

2014-10-16 Thread 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 supported Signed-off-by: Bastian Bittorf