On Monday 28 March 2005 12:55, Thomas Hager wrote: > check your syslog, every cyrus process logs the logged in user. > do sth like: > > egrep '^.*pop3d.*login: .* <user> .*$' /path/to/your/logfile | tail -1 > > and replace <user> with the locked mailbox. this should output the last > process handling the mailbox.
It's bad way. :-( Normal: Mar 28 09:52:22 local6 pop3[11210]: login: xxx.xxxxx.xx [xxx.xxx.xxx.xxx] <user> plaintext User logged in Locked: Mar 28 14:59:26 local6 pop3[27696]: login: xxx.xxxxx.xx [xxx.xxx.xxx.xxx] <user> plaintext User logged in Mar 28 14:59:26 local6 pop3[27696]: Unable to lock maildrop for <user>: Mailbox is locked by POP server Mar 28 15:00:46 local6 pop3[28359]: login: xxx.xxxxx.xx [xxx.xxx.xxx.xxx] <user> plaintext User logged in Mar 28 15:00:46 local6 pop3[28359]: Unable to lock maildrop for <user>: Mailbox is locked by POP server Mar 28 15:03:15 local6 pop3[28182]: login: xxx.xxxxx.xx [xxx.xxx.xxx.xxx] <user> plaintext User logged in Mar 28 15:03:15 local6 pop3[28182]: Unable to lock maildrop for <user>: Mailbox is locked by POP server All lines will be found by regexp. I need to check some next lines for look "Unable to lock maildrop" string at this case. :-( -- Regards, Sergey --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
