Summary: | Courier-authlib fails to start with baselayout-1.12.0_pre5. Other daemons may be affected as well. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Miroslaw Poray-Zbrozek <poray> |
Component: | [OLD] baselayout | Assignee: | Scott Taylor (RETIRED) <swtaylor> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | gurligebis, net-mail+disabled, uberlord, wicher |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Miroslaw Poray-Zbrozek
2005-08-18 15:28:31 UTC
I can verify that this problem also occurs with the new 1.12.0_pre6 version of baselayout: # /etc/init.d/courier-authlib start * Starting courier-authlib: authdaemond ... pidof: invalid options on command line! [ !! ] This is with the following package versions: sys-apps/baselayout-1.12.0_pre6 net-libs/courier-authlib-0.57 net-mail/courier-imap-4.0.4 Please also see Bug 98745 (apparently the newer baselayout's causes problems with "courier-authlib" + "courier-imap" but not with the full "courier" package, although I have not tested the latter myself) I am aswell getting this error with 1.12.0_pre5 and 1.12.0_pre6 of baselayout * Starting courier-authlib: authdaemond ... pidof: invalid options on command line! [ !! ] Im thinking in the source in 'start-stop-daemon' the pidof command has the wrong argument? I can confirm that baselayout-1.12.0_pre6 still behaves the same way and the same workaround in /lib/rcscripts/sh/rc-daemon.sh fixes it. Could someone test editing the courier-authlib init script and changing line 30 to read /usr/bin/env $logger -- -pid="$pidfile" -start "${AUTHLIB}/${AUTHDAEMOND}" I don't think that rc-daemon.sh is at fault here - it's the faulty calling of start-stop-daemon again. I changed line # 30 in /etc/init.d/courier-authlib according to your suggestion and it does fix the problem. Courier Authlib now starts without any problem with the unaltered rc-daemon.sh from baselayout-1.12.0_pre6 (meantime I updated my baselayout but the same should be the case with 1.12.0_pre5). If I manually runs this, it starts fine, so it has to be something with baselayout. jupiter ~ # source /etc/courier/authlib/authdaemonrc jupiter ~ # AUTHLIB="/usr/lib/courier/courier-authlib" jupiter ~ # AUTHDAEMOND="authdaemond" jupiter ~ # pidfile="/var/run/authdaemon.pid" jupiter ~ # logger="/usr/sbin/courierlogger" jupiter ~ # start-stop-daemon --quiet --start --pidfile "$pidfile" -- exec /usr/bin/env -- - $logger -pid="$pidfile" -start "${AUTHLIB}/ ${AUTHDAEMOND}" jupiter ~ # cd /var/lib/init.d/started/ jupiter started # ln -s /etc/init.d/courier-authlib Then I can start courier, since it sees courier-authlib as if it was started by init. (In reply to comment #4) > Could someone test editing the courier-authlib init script and changing line 30 > to read > /usr/bin/env $logger -- -pid="$pidfile" -start "${AUTHLIB}/${AUTHDAEMOND}" > I don't think that rc-daemon.sh is at fault here - it's the faulty calling of > start-stop-daemon again. That works fine :-) Fixed in 0.57-r1 - or just re-emerge your current version. *** Bug 103602 has been marked as a duplicate of this bug. *** |