Bug 115594 - if dovecot hangs, it cannot be restarted
if dovecot hangs, it cannot be restarted
Product: Fedora
Classification: Fedora
Component: dovecot (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: John Dennis
Depends On:
  Show dependency treegraph
Reported: 2004-02-13 13:31 EST by Luigi Iotti
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-05-19 06:26:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Luigi Iotti 2004-02-13 13:31:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; 

Description of problem:
If for some reason dovecot daemon dies (for ex. is killed) the 
service can not be restarted by simply issuing 
service dovecot start
service dovecot restart

This behaviour is due to /etc/init.d/dovecot script, that checks the 
presence of the lock subsystem file. If present, the script does not 
restart the service, so I have to manually delete the lock file 
( /var/lock/subsys/dovecot )
I suggest to the maintainer of the package to apply the following 
patch that simply eliminates this check:

--- dovecot.bak 2003-09-23 18:05:20.000000000 +0200
+++ dovecot     2004-02-13 18:29:59.000000000 +0100
@@ -17,13 +17,11 @@
 start() {
        # Check if dovecot is already running
-       if [ ! -f /var/lock/subsys/dovecot ]; then
            echo -n $"Starting $prog: "
            daemon /usr/sbin/dovecot
            [ $RETVAL -eq 0 ] && touch /var/lock/subsys/dovecot
-       fi
 stop() {

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.service dovecot start
2.killall dovecot
3.service dovecot start
The dovecot service is not restarted

Additional info:
Comment 1 Jeremy Katz 2004-02-17 19:40:38 EST
Fixed in next build

Note You need to log in before you can comment on or make changes to this bug.