I noticed that the PID of a just started imapproxyd is different from the PID 
written to /var/run/imapproxy.pid. Grep uses the PID in this file and doesn't 
find the process.

The initscript uses the --background option of start-stop-daemon, perhaps 
there is some interference with the "foreground_mode no" setting in the 
default imapproxy.conf file. Setting it to yes fixes the bug for me.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to