Re: [rdiff-backup-users] rdiff-backup fails

[Kevin Spicer]

On Sun, 2005-08-07 at 11:37 -0700, Ben Escoto wrote:
> No it doesn't.  I'm not sure how that could be accomplished.  What is
> the difference between a failed rdiff-backup process that aborted in
> the middle and one still in progress?
> 
> We could 1) read through the entire backup and look for recently
> written files, 2) read the process table and look for an existing
> rdiff-backup, or 3) have rdiff-backup fork a thread that updates the
> mtime on some file every minute.  #3 seems the best out of these but
> all seem ugly enough not to be worth doing.

What about just getting an exclusive lock on a file using flock.  If you
can't get the lock then there is another rdiff-backup in progress, if
rdiff-backup fails then the process exiting will release the lock. 

=================================================================

BMRB 
http://www.bmrb.co.uk
_________________________________________________________________
This message (and any attachment) is intended only for the 
recipient and may contain confidential and/or privileged 
material.  If you have received this in error, please contact the 
sender and delete this message immediately.  Disclosure, copying 
or other action taken in respect of this email or in 
reliance on it is prohibited.  BMRB Limited accepts no liability 
in relation to any personal emails, or content of any email which 
does not directly relate to our business.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++