consider the start() function: start() { ebegin "Starting service scan" start-stop-daemon --start --exec /usr/bin/svscan \ --background --make-pidfile \ --pidfile /var/run/svscan.pid -- /service eend $? } i have changed mine to this in order to clean up the environment inherited by all supervised daemons (passing along only PATH): start() { ebegin "Starting service scan" env - PATH="$PATH" start-stop-daemon --start --exec /usr/bin/svscan \ --background --make-pidfile \ --pidfile /var/run/svscan.pid -- /service eend $? } even this is a bit weird, you wind up with a PATH like this: PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/sbin:/usr/sbin apparently somewhere during system init the PATH entries get duplicated.
No idea what installs /etc/init.d/svscan; reopen with exact ebuild name and version.
sys-process/daemontools-0.76-r5 there was no input field for that in the bug submission form.
Thanks.
this is already fixed in baselayout-2 with env whitelisting