pgf wrote:
> Well, kill is an ash builtin, so without the full path, that's what
> you're getting -- but that alone doesn't explain why it doesn't do its
> job. (It's unlikely to be an internal ash problem in any case -- ash is
> a very good shell.)
>
Thanks Paul - yes, contrary to what I expected, /bin/kill is not the
same as kill:
Code:
--------------------
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
tc@pCP:~$ kill --help
sh: bad signal name '-help'
--------------------
So that explains the apparent anomaly with the path, but as you say, it
doesn't explain why the ash version isn't doing its job.
Thanks for the other tips - very useful.
And thanks too for the alternative approach that you posted earlier. I
haven't had time to study it, but it certainly looks more
straightforward than this udev approach.
------------------------------------------------------------------------
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
