Package: dovecot-common Version: 1:1.1.13-2 Severity: normal /etc/init.d/dovecot is quite strange, IMHO.
I noticed that while all other daemons are reporting correctly when they boot up: ... Sat Apr 11 17:49:08 2009: Starting Postfix Mail Transport Agent: postfix. Sat Apr 11 17:49:08 2009: Starting S.M.A.R.T. daemon: smartd. Sat Apr 11 17:49:09 2009: Starting FTP server: vsftpd. Sat Apr 11 17:49:09 2009: Starting NTP server: ntpd. ... dovecot is not (like it's never started?). Further inspection revealed that this is dependent on VERBOSE env. variable, but I think these messages should be unconditional, like in other packages. But dovecot also does something that other packages don't, it always spits out the following: Sat Apr 11 17:49:21 2009: Info: If you have trouble with authentication failures, Sat Apr 11 17:49:21 2009: enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork I don't think these two lines belong to the boot sequence, what if all other packages decided they could point out to some faq or similar, the screen would be cluttered beyond comprehension. IMHO, those two lines should be eliminated, and appropriate warning put to some README.* file in /usr/share/doc/dovecot. Finally, the last objection to the dovecot startup script has to do with performance. My (userspace) bootup sequence takes about 26 seconds (yeah, fast disk), of which 12 is spent in /etc/init.d/dovecot. That is just not right, that dovecot takes almost as much time to go up as ALL the other daemons and scripts on the system (dozens of them). Further inspection revealed that ntp-wait command is the culprit. While I read and understood the explanation for such behaviour, I think it should be workaround in a different way, such that boot sequence is not slowed down that much. Actually, I think such incantation would never work because dovecot is started right after the ntp daemon, and 12 seconds is probably not enough to get it syncronized properly in such a short time. So it probably just timeouts and proceeds like ntp-wait was never run (haven't tested this, remind you, just an opinion). Except it wasted a lot of time, of course. So this whole report is actually 3 smaller bug reports, but they are all about the same file, /etc/init.d/dovecot. What I would like to see is that dovecot starts instantly (in less then a second) printing only one line (when everything is OK, of course): Starting IMAP/POP3 mail server: dovecot. That is what all other packages do, so why would dovecot be so different? -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.28 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=hr_HR (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/bash Versions of packages dovecot-common depends on: ii adduser 3.110 add and remove users and groups ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co ii libc6 2.9-6 GNU C Library: Shared libraries ii libcomerr2 1.41.3-1 common error description library ii libdb4.7 4.7.25-6 Berkeley v4.7 Database Libraries [ ii libgssapi-krb5-2 1.6.dfsg.4~beta1-13 MIT Kerberos runtime libraries - k ii libk5crypto3 1.6.dfsg.4~beta1-13 MIT Kerberos runtime libraries - C ii libkrb5-3 1.6.dfsg.4~beta1-13 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.15-1 OpenLDAP libraries ii libmysqlclient15off 5.0.77-1 MySQL database client library ii libpam-runtime 1.0.1-9 Runtime support for the PAM librar ii libpam0g 1.0.1-9 Pluggable Authentication Modules l ii libpq5 8.3.7-1 PostgreSQL C client library ii libsqlite3-0 3.6.12-1 SQLite 3 shared library ii libssl0.9.8 0.9.8g-16 SSL shared libraries ii openssl 0.9.8g-16 Secure Socket Layer (SSL) binary a ii ucf 3.0018 Update Configuration File: preserv ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime dovecot-common recommends no packages. Versions of packages dovecot-common suggests: ii ntp 1:4.2.4p6+dfsg-1 Network Time Protocol daemon and u ii ntpdate 1:4.2.4p6+dfsg-1 client for setting system time fro -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
