Sam Morris wrote:
> On Sat, 2007-03-31 at 13:17 +0200, Jeroen van Wolffelaar wrote:
>
>> On Sat, Mar 31, 2007 at 12:09:59PM +0100, Sam Morris wrote:
>>
>>> # /etc/init.d/imapproxy stop
>>> Not running: imapproxy.
>>>
>>> # ps 12192
>>> PID TTY STAT TIME COMMAND
>>> 12192 ? Sl 0:06 /usr/sbin/imapproxyd -f /etc/imapproxy.conf
>>>
>> - Does /var/run/imapproxy.pid exist, and if so, what does it contain?
>>
>
> The wrong pid (8319)
>
:-?
>> - With what version of the init script was imapproxy started?
>>
>
> 1.2.4-10 -- I think.
>
Well... this must be it, I think.
Does killing imapproxy and starting it with the new version (1.2.4-10.1)
work ?
Stopping should work then. If not, then it's a nasty, persistent, bug.
>> - What's the md5 of /etc/init.d/imapproxy?
>>
>
> f0578d204fdca62902eeb4ca090a1dd1 /etc/init.d/imapproxy
>
This matches with 1.2.4-10.1
I assume this was started by -10, upon upgrade, it wasn't killed (for
obvious reasons) and so -10.1 can't stop it.
If I'm wrong, then I don't know what happened.
I have since tested this as much as I could, and I have it installed in
two production servers. I haven't noticed any problems yet :-O
All feedback is appreciated.
J.L.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
