Christopher L. Barnard wrote:
<> But what procmail appears to be doing now is consantly fighting over the lock
<> on my mailspool file. From my procmail log:
<> [...]
<> procmail: [3178] Thu Sep 11 09:34:58 2003
<> procmail: Locking "/var/mail/cbar44.lock"
<> procmail: [3178] Thu Sep 11 09:35:06 2003
<> procmail: Locking "/var/mail/cbar44.lock"
<> procmail: [3178] Thu Sep 11 09:35:14 2003
<> procmail: Locking "/var/mail/cbar44.lock"
<> procmail: [3178] Thu Sep 11 09:35:22 2003
<> procmail: Locking "/var/mail/cbar44.lock"
<> procmail: [3178] Thu Sep 11 09:35:30 2003
<> procmail: Locking "/var/mail/cbar44.lock"
<> procmail: [3178] Thu Sep 11 09:35:38 2003
<> procmail: Locking "/var/mail/cbar44.lock"
<> [...]
<>
<> If I delete the lockfile as root, I will get one message and then the lock
<> file comes back and the log continues to fill as above.
and:
<> Unfortunately that is not it. While yes my home directory is mounted
<> via NFS, it is mounted from a server running the same OS (Solaris) and
<> binaries on the NFS server run fine on the NFS clients. My mailspool is
<> NFS mounted from the mailserver, which is also the same OS, but it has
<> its own binaries because I am paranoid.
Hmmm ... My gut is telling me to point a finger at NFS locking. Have you
checked that all the sundry RPC stuff is running (statd, lockd, etc.)?
Have either your $HOME server or the mailhub been rebooted (stale nfs
handles, p'raps?)
You said you'd been checking the MTA logs; I presume there's no direct
evidence of a procmail problem in there, but are there any error lines
that might be remotely the cause?
Reto
--
R A Lichtensteiger rali(_at_)tifosi(_dot_)com
9. Ents and Elves dispute over title of "first-born". Elrond has Quickbeam
made into an armoire; Treebeard grinds Glorfindel into mulch.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail