> > > unlock the file > > > > > > The cleaner you mentioned: run it every 15 minutes, compare the > > > date/time on the lockfile, if more than 15 minutes old, grab the PID, > > > and kill the job, remove the lock. > > > > Correct. Actually, you can make it a lot better: If the lockfile exists, then kill -0 the PID to see if it is still live. If not, blow away the lockfile. If still alive and older than N minutes, blow away the PID and break the lock. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- waiting for new files in a directory Dan Langille
- Re: waiting for new files in a directory Mark Murray
- Re: waiting for new files in a directory Dan Langille
- Re: waiting for new files in a directory Dima Dorfman
- Re: waiting for new files in a directory Dan Langille
- Re: waiting for new files in a directory Mark Murray
- Re: waiting for new files in a directory Peter Pentchev
- Re: waiting for new files in a directory Dan Langille
- Re: waiting for new files in a directory Peter Pentchev
- Re: waiting for new files in a directory Mike Bristow
- Re: waiting for new files in a dire... Peter Pentchev
- Re: waiting for new files in a ... Peter Pentchev
- Re: waiting for new files in a directory Dan Langille
- Re: waiting for new files in a directory Jack Rusher
- Re: waiting for new files in a directory Dan Langille
- Re: waiting for new files in a directory Alfred Perlstein