[source] procd: update procd.sh to disallow signal-numbers, enforce signal-names

[LEDE Commits]

jow pushed a commit to source.git, branch lede-17.01:
https://git.lede-project.org/be7480cb5a5a4879f41acb6e4f11c8759d178b75

commit be7480cb5a5a4879f41acb6e4f11c8759d178b75
Author: Bastian Bittorf <bb at npl.de>
AuthorDate: Fri Jan 13 20:22:51 2017 +0100

    procd: update procd.sh to disallow signal-numbers, enforce signal-names
    
    A given signal-name is now converted to the corresonding number. In general
    it's good style to use names (readability) and it's more portable: signal
    numbers can be architecture-dependent, so we are more safe giving names.
    
    A real world example is signal 10, which is BUS on ramips and USR1 on PPC.
    
    All users of 'procd_send_signal' must change their code to reflect this.
    
    Signed-off-by: Bastian Bittorf <bb at npl.de>
---
 package/system/procd/files/procd.sh | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/package/system/procd/files/procd.sh b/package/system/procd/files/procd.sh
index 8f18cda..a1b9f2f 100644
--- a/package/system/procd/files/procd.sh
+++ b/package/system/procd/files/procd.sh
@@ -213,9 +213,12 @@ _procd_set_param() {
 			json_add_string "" "$@"
 			json_close_array
 		;;
-		nice|reload_signal)
+		nice)
 			json_add_int "$type" "$1"
 		;;
+		reload_signal)
+			json_add_int "$type" $(kill -l "$1")
+		;;
 		pidfile|user|seccomp|capabilities)
 			json_add_string "$type" "$1"
 		;;