Re: setlock oddity - stale lock file?

Charles Cazabon wrote:

> I've run into a situation where setlock appears to have stopped running it's
> child due to the presence of a stale lockfile, which I thought it was immune
> to.
...
>   0-59/5 7-17 * * * ~/bin/setlock -nx /tmp/getmail.lock getmail -q
...
> Can anyone explain what happened here?

"-x: If fn cannot be opened (or created) or locked, setlock exits zero."

According to the source, it also suppresses the error message.  Try
running it without the -x option to see what it reports.

-- 
Regards,
  Daryl Tester

"My god, it's full of 'car's!"  -  "LISP", http://xkcd.com/c224.html