chill wrote:
> 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.
>
Hmm, this is odd - /bin/kill IS the same as the default kill.
Code:
--------------------
tc@pCP:~$ type kill; which -a kill
kill is a shell builtin
/bin/kill
tc@pCP:~$ ll /bin/kill
lrwxrwxrwx 1 root root 7 Jan 1 1970 /bin/kill -> busybox
--------------------
But it behaves differently:
Code:
--------------------
tc@pCP:~$ kill --help
sh: bad signal name '-help'
tc@pCP:~$ /bin/kill --help
BusyBox v1.31.1 (2020-12-18 22:25:41 EST) multi-call binary.
Usage: kill [-l] [-SIG] PID...
Send a signal (default: TERM) to given PIDs
-l List all signal names and numbers
--------------------
------------------------------------------------------------------------
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
