rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Kevin Spicer
Subject: Re: [rdiff-backup-users] rdiff-backup fails
Date: Mon, 08 Aug 2005 07:28:24 +0100

On Sun, 2005-08-07 at 19:42 -0700, Ben Escoto wrote:
> >>>>> Kevin Spicer <address@hidden>
> >>>>> wrote the following on Sun, 07 Aug 2005 21:03:29 +0100
> 
> > 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. 
> 
> Is locking portable though?  

I guess that depends on how python implements it.  I've only got
experience of doing this with perl, and perl emulates flock if the
underlying platform does't support it.  Its certainly a useful check to
make and may well save people some pain.  It may not work on some
platforms, but as its a check not a feature I guess thats really not so
important - especially as the majority of users will be using linux or
some modern unix which will support flock.  You could fallback to
writing the process PID to the file and then checking to see if that
process is running when another process starts. 

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

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.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++





reply via email to

[Prev in Thread] Current Thread [Next in Thread]