Please guard the inetd.conf checks

Bug #208411 reported by Adam Conrad
2
Affects Status Importance Assigned to Milestone
dovecot (Debian)
Fix Released
Unknown
dovecot (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The dovecot init scripts do some clever checks of inetd.conf to see if another imap server is meant to be running on the system, but as we don't ship an inetd by default anymore, this spews noisy output on a default Ubuntu setup due to inetd.conf not existing.

If that entire block could be guarded with an "if [ -f /etc/inetd.conf ]; then ... fi", it would be much prettier. :)

Related branches

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dovecot - 1:1.0.10-1ubuntu4

---------------
dovecot (1:1.0.10-1ubuntu4) hardy; urgency=low

  * debian/dovecot-common.init
    - Check to see if there is an /etc/inetd.conf. (LP: #208411)

 -- Chuck Short <email address hidden> Fri, 28 Mar 2008 15:52:57 -0400

Changed in dovecot:
status: New → Fix Released
Changed in dovecot:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.