Re: checkrestart and dovecot

2011-11-28 Thread Andrew McGlashan
[not the machine running dovecot] # checkrestart Found 1 processes using old versions of upgraded files (1 distinct program) (1 distinct packages) Of these, 1 seem to contain init scripts which can be used to restart them: The following packages seem to have init scripts that could be used

Re: checkrestart and dovecot

2011-11-17 Thread Andrew McGlashan
Hi, On 16/11/2011 10:27 PM, Eduardo M KALINOWSKI wrote: I believe these are the worker processes spawned by the main dovecot server, one for each connection a user makes. They only go away when the user disconnects, even if the main server is restarted, in order not to forcedly disconnect

Re: checkrestart and dovecot

2011-11-17 Thread Andrew McGlashan
Hi, They are back, after the reboot, but not right away... looks like I'll have to report a bug. Now, how to tell which old files are the problem On 18/11/2011 1:44 AM, Andrew McGlashan wrote: I couldn't see any evidence of any worker processes. The problem has persisted. So ... I've

Re: checkrestart and dovecot

2011-11-17 Thread Bob Proulx
Andrew McGlashan wrote: They are back, after the reboot, but not right away... looks like I'll have to report a bug. Now, how to tell which old files are the problem How is your python scripting? The checkrestart script is simply a python script. If you have favorite methods of

Re: checkrestart and dovecot

2011-11-16 Thread Eduardo M KALINOWSKI
On Ter, 15 Nov 2011, Andrew McGlashan wrote: Andrew McGlashan wrote: # checkrestart Found 2 processes using old versions of upgraded files (1 distinct program) (1 distinct packages) These processes do not seem to have an associated init script to restart them: dovecot-imapd: 18981

Re: checkrestart and dovecot

2011-11-15 Thread Bob Proulx
/lib/dovecot/imap No updates since these processes were started. How do I find out which is the offending component? You would want to restart 'dovecot'. # service dovecot restart The checkrestart script can't deduce the right restart script since the programs running are in dovecot-imapd

Re: checkrestart and dovecot

2011-11-15 Thread Andrew McGlashan
/usr/lib/dovecot/imap 14795 /usr/lib/dovecot/imap No updates since these processes were started. How do I find out which is the offending component? You would want to restart 'dovecot'. # service dovecot restart The checkrestart script can't deduce the right restart script since

Re: checkrestart and dovecot

2011-11-15 Thread Bob Proulx
Andrew McGlashan wrote: These processes do not seem to have an associated init script to restart them: dovecot-imapd: 18981 /usr/lib/dovecot/imap 14795 /usr/lib/dovecot/imap Yes, but I've stopped and restarted dovecot. New processes *later* come up as flagged by

checkrestart and dovecot

2011-11-14 Thread Andrew McGlashan
Hi, I've got the following: # checkrestart Found 2 processes using old versions of upgraded files (1 distinct program) (1 distinct packages) These processes do not seem to have an associated init script to restart them: dovecot-imapd: 18981 /usr/lib/dovecot/imap 14795