Hi!
I have a question on rsync's way to deal with files in use
or files that are modified on the source while they
are transferrred to the destination.
Yes, I searched the web and found
In rsync, transfers are done to a temporary file, which is cut over
atomically, so the transfer either
I've read a few tutorials about how to use rsync via ssh using the
command= functionality to restrict where the user can sync to. I've
got this on the on the destination side in it's ~/.ssh/authorized_keys...
command=rsync --server -vvnlogDtpre.iLsf --timeout=999 .
On Thu, 2010-06-03 at 20:18 +1000, Mark Constable wrote:
I've read a few tutorials about how to use rsync via ssh using the
command= functionality to restrict where the user can sync to. I've
got this on the on the destination side in it's ~/.ssh/authorized_keys...
command=rsync --server
On 2010-06-04, Matt McCutchen wrote:
I've read a few tutorials about how to use rsync via ssh
using the command= functionality to restrict where the
user can sync to.
...
or (my preference) use a single-use rsync daemon. See:
https://bugzilla.samba.org/show_bug.cgi?id=4163
I didn't know
HomeRun4711 (homerun4...@googlemail.com) wrote on 3 June 2010 11:27:
I have a question on rsync's way to deal with files in use
or files that are modified on the source while they
are transferrred to the destination.
[removed]
But what if e.g. a large mailbox file is changed on the source
When I'm running rsync --compare-dest on a local Linux volume (ext4) it
works as expected (duplicate files not created) however when same commands
with same options are run on NTFS USB drive (in my scenario below mounted to
/share/external/sdt5) all the files are copied regardless if they have
On Fri, 2010-06-04 at 01:03 +0100, Sergey Shatokhin wrote:
When I'm running rsync --compare-dest on a local Linux volume (ext4)
it works as expected (duplicate files not created) however when same
commands with same options are run on NTFS USB drive (in my scenario
below mounted to
