Hi, Why do not you shut them out every day? by cron / find find /var/lib/cyrus/proc -mtime +1-print | xargs --no-run-if-empty rm Le 21.01.2011 05:28, Simon Matter a écrit : >> Hi, >> >> Am Donnerstag, den 20.01.2011, 21:02 +0100 schrieb Simon Matter: >>>> Hi, >>>> >>>> I see some very old pid files in /var/lib/cyrus/proc: >>>> >>>> -rw------- 1 cyrus mail 58 9. Nov 21:24 12116 >>>> -rw------- 1 cyrus mail 58 9. Nov 23:56 26636 >>>> -rw------- 1 cyrus mail 46 23. Nov 10:00 30308 >>>> -rw------- 1 cyrus mail 53 3. Dez 21:11 5042 >>>> -rw------- 1 cyrus mail 87 5. Dez 14:54 5623 >>>> -rw------- 1 cyrus mail 53 19. Nov 11:03 7064 >>>> -rw------- 1 cyrus mail 55 21. Dez 11:41 8681 >>>> -rw------- 1 cyrus mail 17 26. Nov 13:59 9610 >>>> ... >>>> >>>> # more 30308 >>>> xxx.dip0.t-ipconnect.de [80.131.xxx.xxx] >>>> >>>> The imapd processes are still running. How to kill them? Just a "kill >>>> pidnumer" for each of them or will that harm any cyrus databases? >>> I think killing the way you said (which means SIGTERM) is not a problem. >>> However, it would be interesting to know what those processes are doing? >>> Maybe you could strace them? >>> I think the newer cyrus-imapd versions have some ways to detect not >>> existing clients while older version waited forever, so what's your >>> version? >> I'm using Cyrus 2.2.13-14+lenny3 on a Debian/Lenny system. > Then I think you don't have those fixes and are expected to see such never > ending processes (pop processes)? > > Simon > > ---- > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ -- Christophe ================== ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
