[ Brock Rozen writes: ]
> If the .archive directory does not exist and mkdigest is run, then digest
> will abort in the middle and the .LOCK file in the digest work directory
> won't be erased...
> It is possible to put some additional checks in somewhere around the abort
> At minimum, a note should be put in the FAQ that before restarting
> mkdigest/digest the lock file needs to be deleted.
If the lock file isn't valid, shlock will remove it. Granted, the
determination of whether or not a lock is valid is a little lame in that
it checks to see if the process ID in the lock file is that of a valid
process, which can be true if the pid has been reassigned, worse yet
if it's reused for a long-running process, so a note about persistent
"Can't lock...lock is valid" messages steering users to look for stale
lock files is entirely appropriate. But I don't think it's any of
abort's business to be cleaning up locks.