Bug#411148: sasl2-bin: "/etc/init.d/saslauthd {stop|restart}" kills instances in unrelated chroots

[Fabian Fagerholm]

severity 411148 normal
merge 320377 411148
thanks

On Fri, 2007-02-16 at 16:58 +0100, Gabor Gombas wrote:
> /etc/init.d/saslauthd does not seem to honour the pidfile, and when
> invoked with the "stop" or "restart" arguments in a chroot, it kills
> unrelated saslauthd instances running in other chroots. This is quite
> painful as it renders unrelated services running in those chroots
> unusable.

I'm afraid our init script is just not clever enough. It should support
multiple instances of saslauthd, whether they are chrooted or not.
However, the etch version "doesn't support multiple instances of
saslauthd", so I'm setting the severity to normal.

I'm merging this with #320377, which concerns the same general issue.

The plan is to introduce multiple-instance support for lenny.

Thanks for reporting this!

-- 
Fabian Fagerholm <fabbe at paniq.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20070224/6943bef9/attachment.pgp