Bug#401348: sasl2-bin: Problem started daemon soon after installed

[Fabian Fagerholm]

On Mon, 2006-12-04 at 11:35 +0100, Ondřej Surý wrote:
> The thing is that you cannot expect /var/run to retain it's contents
> during upgrades.  It was discussed while ago (on debian-something) and
> init.d script should propably recreate /var/run/saslauthd/ when it
> doesn't exists.

It does. To confirm, try this:

$ /etc/init.d/saslauthd stop
Stopping SASL Authentication Daemon: saslauthd.
$ grep START /etc/default/saslauthd
START=yes

$ rmdir /var/run/saslauthd
$ ls -l /var/run | grep sasl
(no output, the dir is gone -- this simulates the case you mention)

$ /etc/init.d/saslauthd start
Starting SASL Authentication Daemon: saslauthd.
$ ls -l /var/run | grep sasl
drwx--x--- 2 root        sasl        4096 2006-12-04 12:58 saslauthd

The dir is recreated with permissions as set by dpkg-statoverride.

It even handles correctly the case where you want the run directory to
be placed anywhere else in the file system. (For Postfix and other
chroot cases.) You do that by setting proper OPTIONS in the default
file, and it picks up the run dir from the -m flag automatically. This
is documented in README.Debian, with an example in the default file.

So I guess that #401348 is about something else, for example incorrect
defaults file, broken init script (failed update? user error?) or
broken / faulty dpkg-statoverride.

Cheers,
-- 
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/20061204/de67dbde/attachment.pgp