I just got a couple calls from some people I work with and have been bouncing emails it seems. I think I tracked it down to a problem with procmail trying to lock files. In my procmail log I get this:
procmail: No match on "charset=.*(koi8|windows-125[15]|big-?5|gb2312)" procmail: Match on ! "^Content-Type: message/" procmail: No match on ! "^Content-Type: multipart/" procmail: Locking "/tmp/.msgid.lock" procmail: Executing "/usr/bin/crm,-u,/home/nomad/crm114,/usr/share/crm114/mailfilter.crm" procmail: No match on "charset=.*(koi8|windows-125[15]|big-?5|gb2312)" procmail: Match on ! "^Content-Type: message/" procmail: No match on ! "^Content-Type: multipart/" procmail: Locking "/tmp/.msgid.lock" procmail: [1756] Tue Jul 27 10:24:21 2004 procmail: Locking "/tmp/.msgid.lock" procmail: [1756] Tue Jul 27 10:24:29 2004 procmail: Locking "/tmp/.msgid.lock" The last 5 lines will continue a while and as more mail comes in, more lock request are added in. If I do a "ps" I can see the procmails start adding up until I have 80 or so and things start failing. The procmail line generating this is: :0fw: /tmp/.msgid.lock | /usr/bin/crm -u /home/nomad/crm114 /usr/share/crm114/mailfilter.crm I changed it to "/tmp/.msgid.lock" from ".msgid.lock" thinking it might be related to an NFS issue but the behaviour is the same. Any thoughts? The spam is killing me. :wq! --------------------------------------------------------------------------- Robert L. Harris | GPG Key ID: E344DA3B @ x-hkp://pgp.mit.edu DISCLAIMER: These are MY OPINIONS ALONE. I speak for no-one else. With Dreams To Be A King First One Should Be A Man - Manowar
signature.asc
Description: Digital signature