Package: dovecot-common
Version: 1.0.rc15-2etch1
In the /etc/init.d/dovecot script, the "start" option processes the
"protocols" line in dovecot.conf file and doesn't start dovecot unless there
is an entry there that isn't in the inetd.conf file. The "restart" option
doesn't do any checking and will always start the daemon.
This means that with the default install (which has "protocols" commented
out), using "/etc/init.d/dovecot restart" will start dovecot, but the rc*.d
links won't. If you manually start dovecot after the install (with
"/etc/init.d/dovecot restart"), it will silently fail to start at the next
reboot.
It would presumably also cause problems if someone was using inetd and
issued a restart command on dovecot.
I'm not an expert, but maybe using:
$0 stop
sleep 1
$0 start
would be better than:
start-stop-daemon --stop --quiet --oknodo --exec $DAEMON
sleep 1
start-stop-daemon --start --quiet --oknodo --exec $DAEMON
I also think that having the default install leave dovecot configured so it
won't start is not a good idea.... having the default protocols line
("protocols = imap imaps") uncommented or having the start script use the
default commented line if there's not an uncommented one might be better.
Toby
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
