Your message dated Tue, 07 Nov 2006 19:57:04 +0200 with message-id <[EMAIL PROTECTED]> and subject line sasl2-bin: Init script does not allow explicit service start if (auto)START != yes has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: sasl2-bin Version: 2.1.18-4.1 Severity: minor The start/stop script /etc/init.d/saslauthd does not allow to start the saslauthd unless START is set to "yes" by /etc/default/saslauthd or in the calling shell's environment. This is no problem, it is easy to call e.g. START="yes" /etc/init.d/saslauthd start to try the thing out, but the init script should at least tell - the fact that nothing has been started, e.g. "SASL-Authd not started" - the reason, e.g. "because START != yes, see /etc/default/saslauthd" Eventually the script should also exit with someting other than 0 if an error (or another reason not to start) occurs. This especially applies to the second "exit 0" statement which handles missing MECHANISMS. I suggest to change the lines ... --- SNIP --- # If we're not to start the daemon, simply exit if [ "${START}" != "yes" ]; then exit 0 fi # If we have no mechanisms defined if [ "x${MECHANISMS}" = "x" ]; then echo "You need to configure ${DEFAULTS} with mechanisms to be used" exit 0 fi --- SNIP --- ... to something like ... --- SNIP --- # If we're not to start the daemon, simply exit if [ "${START}" != "yes" ]; then echo 'Skipping saslauthd because START is not set to "yes"' echo "See ${DEFAULTS}' exit 2 fi # If we have no mechanisms defined if [ "x${MECHANISMS}" = "x" ]; then echo "You need to configure ${DEFAULTS} with mechanisms to be used" exit 4 fi --- SNIP --- kr Christoph -- System Information: Debian Release: sarge/unstable Architecture: i386 (i686) -- no debconf information
--- End Message ---
--- Begin Message ---Version: 2.1.22-1 Hi, It's a bit unclear which fault this bug report refers to. There are several possibilities: A. The saslauthd init script does not start saslauthd unless START is set to yes in /etc/default/saslauthd. B. The saslauthd init script does not provide enough information on why saslauthd is not started when START != yes. C. The saslauthd init script should exit with a non-zero exit status when START != yes. It is intended behaviour that the init script doesn't start when START is not yes. So for case A, the bug report can be closed. For case B, the issue is a usability bug that doesn't affect any functionality. It has been fixed in 2.1.22-1 (and earlier pre-versions in experimental). Case C is not a bug because the script has been instructed not to start saslauthd. It is thus performing correctly, and should exit with 0 (success). This stems from the behaviour of the current Debian init system. The exit code is saying whether or not the script succeeded in performing its task (nothing, if START != yes), not whether or not the saslauthd daemon was actually started. Since none of the cases can be considered valid at this time, I'm closing this bug for 2.1.22-1. Thanks, -- Fabian Fagerholm <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
--- End Message ---
