Thanks again - very instructive, and it gives me something to look into tomorrow. I know that the path available to a script called by udev is indeed rather shorter than the one available under a user shell (i'll post it again tomorrow). But does this make a difference if a command is part of busybox? If it's part of busybox, does it even bother to look in the path for a separate binary? Or do I have this wrong, and the busybox commands ARE all separately linked to somewhere in the path? And assuming the busybox built-in version is found, what could cause a built-in command to fail when called in the udev environment (on some setups), whereas the explicitly specified binary doesn't?
And the other thing that's puzzling me - what could explain the 'stop' part of the start-stop-daemon working on some setups and not others, when the setups are based on the same pCP base. ------------------------------------------------------------------------ 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
