Your message dated Tue, 07 Nov 2006 19:59:31 +0200
with message-id <[EMAIL PROTECTED]>
and subject line sasl2-bin: init.d script should give error that it's not
configured
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,
This bug has been fixed in version 2.1.22-1 (and earlier pre-versions in
experimental). The init script now outputs an informative message,
telling the sysadmin how to enable saslauthd.
Thanks,
--
Fabian Fagerholm <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
--- End Message ---
