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.19-1.5
Severity: wishlist
The init.d script just quits without any information when the system is
not setup in /etc/defaults/saslauthd. It should give an error
indicating that. This is probably a bug with a lot of init scripts.
Bill
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages sasl2-bin depends on:
ii base-passwd 3.5.10 Debian base system master password
ii libasn1-6-heimdal 0.6.3-12 Libraries for Heimdal Kerberos
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
ii libcomerr2 1.38-2 common error description library
ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [
ii libgssapi1-heimdal 0.6.3-12 Libraries for Heimdal Kerberos
ii libkrb-1-kerberos4kth 1.2.2-11.3 Kerberos Libraries for Kerberos4 F
ii libkrb5-17-heimdal 0.6.3-12 Libraries for Heimdal Kerberos
ii libldap2 2.1.30-12 OpenLDAP libraries
ii libpam0g 0.76-23 Pluggable Authentication Modules l
ii libroken16-kerberos4kth 1.2.2-11.3 Roken Libraries for Kerberos4 From
ii libsasl2 2.1.19-1.5 Authentication abstraction library
ii libssl0.9.7 0.9.7g-2 SSL shared libraries
sasl2-bin recommends no packages.
-- 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 ---
