I had the same situation. I finish by rebooting to solve the 1st update lockout on the first occurrence. On the second, I just change conveniently the upstart script by the genuine one and the return code was OK for the update to complete.
In order to find a clean upstart-based solution, I try to switch to "expect daemon" in /etc/init/dovecot.conf to insure upstart being capable of tracking dovecot process, but I've got the same hangup problem.
Question is, is upstart capable of tracking program launched in a unprivileged way by the daemon ?
The only similar reference I'm thinking of is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582745 .
I had the same situation. I finish by rebooting to solve the 1st update lockout on the first occurrence. On the second, I just change conveniently the upstart script by the genuine one and the return code was OK for the update to complete. dovecot. conf to insure upstart being capable of tracking dovecot process, but I've got the same hangup problem. bugs.debian. org/cgi- bin/bugreport. cgi?bug= 582745 .
In order to find a clean upstart-based solution, I try to switch to "expect daemon" in /etc/init/
Question is, is upstart capable of tracking program launched in a unprivileged way by the daemon ?
The only similar reference I'm thinking of is http://