Re: liblockfile L_PID behavior and use of stat atime

2008-02-23 Thread Rob Browning
Rob Browning [EMAIL PROTECTED] 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

Re: liblockfile L_PID behavior and use of stat atime

2008-02-21 Thread Rob Browning
Rob Browning [EMAIL PROTECTED] writes: Someone reported a bug against lockfile-progs, and while investigating I noticed a couple of things about liblockfile that didn't seem quite right. After further investigation, it looks like a lockfile created on a noatime (or relatime?) filesystem,

liblockfile L_PID behavior and use of stat atime

2008-02-19 Thread Rob Browning
Someone reported a bug against lockfile-progs, and while investigating I noticed a couple of things about liblockfile that didn't seem quite right. First of all, if you run lockfile-create foo, which calls lockfile_create() without the L_PID flag, you'll see that the resulting foo.lock file