On Mon, 4 Aug 2008, Timo Sirainen wrote:
It doesn't seem to be that the current logic is working; there is no
program with the PID that's in master.pid, and dovecot (1.0.7 + RHEL
patches) refuses to start.
root: /root$ /sbin/service dovecot start
Starting Dovecot Imap: Error: Dovecot is
Pekka Savola píše v Po 04. 08. 2008 v 12:40 +0300:
On Mon, 4 Aug 2008, Timo Sirainen wrote:
It doesn't seem to be that the current logic is working; there is no
program with the PID that's in master.pid, and dovecot (1.0.7 + RHEL
patches) refuses to start.
root: /root$ /sbin/service
On Aug 2, 2008, at 8:22 PM, Pekka Savola wrote:
It doesn't seem to be that the current logic is working; there is no
program with the PID that's in master.pid, and dovecot (1.0.7 + RHEL
patches) refuses to start.
root: /root$ /sbin/service dovecot start
Starting Dovecot Imap: Error:
On Tue, 1 Jul 2008, Timo Sirainen wrote:
$ /sbin/service dovecot start
Starting Dovecot Imap: Error: Dovecot is already running with PID 10825
(read from /var/run/dovecot/master.pid)
Fatal: Invalid configuration in /etc/dovecot.conf
On Tue, 2008-07-01 at 00:14 +0300, Pekka Savola wrote:
$ /sbin/service dovecot start
Starting Dovecot Imap: Error: Dovecot is already running with PID 10825
(read from /var/run/dovecot/master.pid)
Fatal: Invalid configuration in /etc/dovecot.conf
On Jul 1, 2008, at 12:51 AM, Timo Sirainen wrote:
Is this already a known problem?
Should the start-up logic be made more robust (e.g. check whether a
process corresponding to the PID actually exists)?
It already checks if the PID exists, but it doesn't check what that
process is (and I don't
