how does rsync handle open/buisy files
I'm wondering if anyone that uses rsync hands open files or buisy files. does it copy them over or skip them. At the time of the night I plan to have rsync run no one should be here at the office but sometimes some files get left open or in a bisy state if there machine locks up an they do not tell me so that I can unflag them from the accounting software package so that the files they were working with in the account software gets updated to not being open/ locked. thanks for the info. jack
Jack Malone wrote:
I'm wondering if anyone that uses rsync hands open files or buisy files. does it copy them over or skip them. At the time of the night I plan to have rsync run no one should be here at the office but sometimes some files get left open or in a bisy state if there machine locks up an they do not tell me so that I can unflag them from the accounting software package so that the files they were working with in the account software gets updated to not being open/ locked.
thanks for the info. jack
I've used rsync alot across busy volumes and have yet to encounter a problem with open files. My experiences agrees with this Google result, http://lists.samba.org/archive/rsync/2004-August/010237.html Jason Joines =================================
Jason, On Monday 24 October 2005 07:01, Jason Joines wrote:
Jack Malone wrote: ...
I've used rsync alot across busy volumes and have yet to encounter a problem with open files. My experiences agrees with this Google result, http://lists.samba.org/archive/rsync/2004-August/010237.html
I believe those statements, while not inaccurate, are oversimplified, both w.r.t. to Unix (-alikes) and Windows. In particular, while the most common case in Windows will preclude readers when there is a writer (as stated there) but on Unix systems use of file locking is not common and only the file's permissions govern access, regardless of whether another program has the file open for read, write or both. But on both Windows and Linux, the opposite is true.
Jason Joines
Randall Schulz
Hi, On Monday 24 October 2005 07:18, Randall R Schulz wrote:
Jason,
...
In particular, while the most common case in Windows will preclude readers when there is a writer (as stated there) but on Unix systems use of file locking is not common and only the file's permissions govern access, regardless of whether another program has the file open for read, write or both.
But on both Windows and Linux, the opposite is true.
Oops. That doesn't really make much sense, does it? What I meant to say, and apparently did not finish writing, is that on both Windows and Linux, the common case (exclusive access on Windows and no exclusion on Unix) can be reversed on both systems if the programs first accessing the file choose to do so. Randall Schulz
participants (3)
-
Jack Malone
-
Jason Joines
-
Randall R Schulz