I have a theory that I'd like to test, but I'm not sure how.
I've now methodically repeated my earlier tests on my troublesome Pi3A+. 1) Called from within my own script (bypassing the init.d script), the command 'start-stop-daemon --stop -p $PIDFILE' reports that it has stopped the process, but the process stays running. 2) If I replace that command with 'sudo kill -9 $PID', the process stays running. 3) If I replace that command with 'sudo /bin/kill -9 $PID', the process is successfully killed. 4) From the command line, all three of these methods successfully kill the process. So 1-3 versus 4 shows there's something different about the udev environment compared to a normal user shell. But the theory I want to test is that the start-stop-daemon is using the default kill. I'm guessing that in fact it's simply using the same source code within busybox, so there'll be no way to change that. But if it is instead calling the default binary for the kill command, how can I change the default binary to be the one in /bin? Assuming the default kill command is a symlink to the busybox command, can I replace that symlink with one that points to /bin/kill, and if so, how? If I can do that I could then repeat the test with the start-stop-daemon to see if that has forced it to use /bin/kill. ------------------------------------------------------------------------ chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=113661 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
