Package: cyrus-common-2.2 Version: 2.2.12-0.6 Severity: important Tags: patch User: [EMAIL PROTECTED] Usertags: incorrect-dependency
I just checked the shutdown order in unstable on a machine with dependency based boot sequencing enabled, and discovered a problem with the init.d scripts provided in the cyrus-common-2.2 package. It stops to late and start to early, as it do not depend on $remote_fs which guarantee that /usr/ will be mounted and that it stops before sendsigs. Another issue is that the init.d script list S in its stop runlevel list. This make a useless stop symlink in rcS.d/, and S should not be included there. Here is a patch to solve these issues. diff -ur cyrus-imapd-2.2-2.2.13.orig/debian/cyrus-common-2.2.cyrus2.2.init cyrus-imapd-2.2-2.2.13/debian/cyrus-common-2.2.cyrus2.2.init --- cyrus-imapd-2.2-2.2.13.orig/debian/cyrus-common-2.2.cyrus2.2.init 2008-03-09 08:44:30.000000000 +0100 +++ cyrus-imapd-2.2-2.2.13/debian/cyrus-common-2.2.cyrus2.2.init 2008-03-09 08:45:26.000000000 +0100 @@ -2,10 +2,10 @@ # ### BEGIN INIT INFO # Provides: cyrus-common-2.2 -# Required-Start: $syslog $network -# Required-Stop: $syslog $network +# Required-Start: $remote_fs $syslog $network +# Required-Stop: $remote_fs $syslog $network # Default-Start: 2 3 4 5 -# Default-Stop: S 0 1 6 +# Default-Stop: 0 1 6 # Short-Description: common init system for cyrus 2.2 IMAP/POP3 daemons. # Description: common init system the for cyrus 2.2 IMAP/POP3 daemons. # starts the central cyrus 2.2 master process, which can Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
