Re: liblockfile L_PID behavior and use of stat atime
Rob Browning <email@example.com> writes:
> After further investigation, it looks like a lockfile created on a
> noatime (or relatime?) filesystem, without specifying L_PID, can
> never go stale. The problem is in lockfile_check().
It looks like procmail's lockfile doesn't have this problem since it
doesn't appear to use the atime at all.
Should liblockfile (and everything that depends on it) and procmail's
lockfile have different locking behaviors?
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4