On Monday 27 June 2011, Nico Kadel-Garcia wrote:
On Sat, Jun 25, 2011 at 1:58 PM, Rüdiger Meier <sweet_f_a < at > gmx.de>
wrote:
/.rsync-filter is controlled by client's admin only.
And requires the '-F' option. It's not enabled by default, according
to the man page.
But that's rrsync for. Just force the -F option (simply hardcode it in
rrsync script). To make it real safe you would not even need rrsync -
just hardcode "command="rsync --server -F --whatever".
rsync is never atomic. If you write to file while rsyncing then it
might be broken anyway. Permissions and ownership race is IMO less
fatal.
Much smaller risk, though. It only takes one directory with 200,000
files in it on an older file system to really extend the duration of
rsync operations, even if the files are not individually large.
(Maildir: oh, dear lord, Maildir for people who delete nothing......)
That would set.... interesting time discrepancy issues between the
primary data and the metadata.
On the other hand chmod/chown are very seldom used in opposite to
writing to files because usually files will be created with the final
umask already.
And timestamps mostly doesn't need to be 100% exact.
cu,
Rudi
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
