Last night I began having trouble with locking. I removed my .procmail and
replaced it with an ultra-plain version to see if the locking problem went
away. No luck. I suspect something is amiss outside of my control. I would
like someone to have a look at this and let me know what to bring up with
my sysadmin? I have already spoken to him once, but know help yet.
'procmail -v' output:
procmail v3.10 1994/10/31 written and created by Stephen R. van den Berg
Locking strategies: dotlocking, fcntl(), lockf()
Default rcfile: $HOME/.procmailrc
System mailbox: /usr/mail/$LOGNAME
procmail:  Mon Dec 15 17:48:14 1997
procmail: Locking "/usr/mail/dh.lock"
procmail: Error while writing to "/usr/mail/_VM0Gacme"
procmail: Lock failure on "/usr/mail/dh.lock"
#The above repeats 8 times, at 8 second intervals, then delivers:
procmail: Assigning "LASTFOLDER=/usr/mail/dh"
procmail: Opening "/usr/mail/dh"
procmail: Acquiring kernel-lock
From dh(_at_)west(_dot_)net Mon Dec 15 17:47:09 1997
Subject: Re: Your mail
procmail:  Mon Dec 15 17:48:15 1997
procmail: Notified comsat: "dh(_at_)252144:/usr/mail/dh"
My .procmailrc at the moment:
# begin $HOME/.procmailrc
# clear the log at the start of each session and write the current env;
for diagnostic puposes:
exec="`cp /dev/null $LOGFILE`" exec="`env >> $LOGFILE`"
# end $HOME/.procmailrc