From: Ed W <li...@wi...> - 2011-08-21 23:06:06
|
On 21/08/2011 20:00, Tom Eastep wrote: > > On Aug 21, 2011, at 10:31 AM, Tom Eastep wrote: > >> >> On Aug 21, 2011, at 9:46 AM, Tom Eastep wrote: >>> >>> /usr/bin/lockfile does not store the locker's PID in the file; as far as I can tell, the file always contains '0' (with no newline). Using that program is the preferred way to create a lock file, since doing it in the shell is race-prone. But I'll see what I can do for 4.4.23. >> >> >> Ed, >> >> I've added stale lock file detection/removal in the 4.4.23 branch. >> > > I've also discovered that the way that I'm invoking lockfile is rather braindead. I've also corrected that in the 4.4.23 branch and, if I create another 4.4.22 point release, I'll include it there as well. Many thanks - I will look into the changes ASAP Ed W |