Timeline for Operation referenced in sudoers still fails on kill command
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 12, 2024 at 19:26 | history | edited | telcoM | CC BY-SA 4.0 | added missing 2>/dev/null |
| Mar 12, 2024 at 19:25 | comment | added | telcoM | Oops, I forgot that the kill -0 test needs a 2>/dev/null to silence the error message. And the command not found should be fixed by specifyingstart-stop-daemon using a full path, i.e. /usr/sbin/start-stop-daemon. | |
| Mar 12, 2024 at 19:11 | comment | added | Norbert | Thanks! I've tried as you suggested and inserted your code block. But it gives the following output: nodered@pi:~$ /etc/init.d/connman restart /etc/init.d/connman: line 13: kill: (1527) - Operation not permitted Restarting Connection Manager /etc/init.d/connman: line 64: start-stop-daemon: command not found Line 64 is at the end of this block: do_stop() { # kill the script monitoring execution if [ "X${pid=$(pidof -x /usr/sbin/connmand-watch.sh)}" != "X" ]; then kill $pid fi start-stop-daemon --stop --name connmand --quiet } | |
| Mar 12, 2024 at 17:43 | history | answered | telcoM | CC BY-SA 4.0 |