IMHO it's easiest not to lock $LOGFILE, just living with the occasional
interleavings of entries.
Regards,
--
Rick Troxel Rick_Troxel(_at_)nih(_dot_)gov
rick(_at_)helix(_dot_)nih(_dot_)gov
http://www.dc-sage.org/bios/rick_troxel 301/435-2983
/////////////////////////////////////////////////////////////////
All effort and exertion put forth by man from the fullness of his
heart is worship, if it is prompted by the highest motives and
the will to do service to humanity. --Abdu'l-Baha
On Fri, 17 Oct 1997, Steve Kelley wrote:
steve.kelley> LOGFILE=$HOME/.procmail/procmail.log
steve.kelley>
steve.kelley> From the mail server system a given "procmail.log" file
steve.kelley> will become inaccessible. The procmail daemons that are
steve.kelley> running for the given account become hung. You can't send
steve.kelley> them any kill signal. The processes can't be killed
steve.kelley> without a system reboot.
steve.kelley>
steve.kelley> The other thing that is strange is a "ls -l
steve.kelley> $HOME/.procmail/procmail.log" will also hang when in this
steve.kelley> state. It can't be killed either. You can do commands
steve.kelley> against other files in $HOME/.procmail. You just can't
steve.kelley> run any command that touches the procmail.log file.
steve.kelley>
steve.kelley> I know that you can use LOCKFILE or "local lock files(:)"
steve.kelley> for recipes.
steve.kelley>
steve.kelley> What type locking is done for the "LOGFILE"?
steve.kelley> Does the locking depend on the "Locking strategies" that
steve.kelley> procmail was built with?