--
upstart unable to correctly track dovecot daemon when managesieve plugin is
enabled https://bugs.launchpad.net/bugs/646858
You received this bug notification because you are a direct subscriber
of a duplicate bug (648605).
Status in “dovecot” package in Ubuntu: Fix Released
Status in “upstart” package in Ubuntu: New
Status in “dovecot” source package in Maverick: Fix Released
Status in “upstart” source package in Maverick: New
Bug description:
When the managesieve plugin is enabled it seems that dovecot forks once more
than what upstart expects. Upstart tracks the wrong pid with "expect fork" set.
============
Original description
Binary package hint: dovecot-postfix
Dovecot on Maverick is now using upstart to launch dovecot. When dovecot-postfix
is installed, the dovecot must have some component as root (for SASL
authentification purpose, in order to write to postfix chroot). Problem is, the
system can start dovecot on boot, but any attempt into using restart dovecot
will result in a hang of upstart. CTRL+C can cancel it, but then dovecot is in a
strange state, with half the processus presents in memory. This is not the
correct behavior, as we except a smooth restart of such an important service of
the mail (especially if SASL authentification of postfix is involved).
As a workaround, I replace the symlink to upstart by the old init.d original
script from ubuntu 10.04.1.
I try to figure out a clean solution, but apparently this is inherent to upstart
and explains why some package, such as apache, did not go on the upstart train
already.
Dear Mr. Jean-Baptiste,
Thanks a lot.
I am using squirrelmail on Ubuntu 10.10 now. Dovecot is working fine.
Regards,
Satish
(Col. SC Sood(Retd))
09216508708
_______ _______ _______ _______ ____
From: Jean-Baptiste Lallement <email address hidden>
To: <email address hidden>
Sent: Fri, 22 October, 2010 2:53:11 PM
Subject: [Bug 646858] Re: upstart unable to correctly track dovecot daemon when
managesieve plugin is enabled
** Tags added: maverick potential
** Tags removed: regression-
-- /bugs.launchpad .net/bugs/ 646858
upstart unable to correctly track dovecot daemon when managesieve plugin is
enabled
https:/
You received this bug notification because you are a direct subscriber
of a duplicate bug (648605).
Status in “dovecot” package in Ubuntu: Fix Released
Status in “upstart” package in Ubuntu: New
Status in “dovecot” source package in Maverick: Fix Released
Status in “upstart” source package in Maverick: New
Bug description:
When the managesieve plugin is enabled it seems that dovecot forks once more
than what upstart expects. Upstart tracks the wrong pid with "expect fork" set.
============
Original description
Binary package hint: dovecot-postfix
Dovecot on Maverick is now using upstart to launch dovecot. When dovecot-postfix
is installed, the dovecot must have some component as root (for SASL
authentification purpose, in order to write to postfix chroot). Problem is, the
system can start dovecot on boot, but any attempt into using restart dovecot
will result in a hang of upstart. CTRL+C can cancel it, but then dovecot is in a
strange state, with half the processus presents in memory. This is not the
correct behavior, as we except a smooth restart of such an important service of
the mail (especially if SASL authentification of postfix is involved).
As a workaround, I replace the symlink to upstart by the old init.d original
script from ubuntu 10.04.1.
I try to figure out a clean solution, but apparently this is inherent to upstart
and explains why some package, such as apache, did not go on the upstart train
already.
To unsubscribe from this bug, go to: /bugs.launchpad .net/ubuntu/ +source/ dovecot/ +bug/646858/ +subscribe
https:/