similar to: Checksum Behavior Change

Hi rsync folks, I understand that by default, rsync will re-copy a file if the timestamp differs, but the size is the same. Sometimes, though, I have large files whose mtime have been changed but are otherwise identical. It seems a solution to this is --checksum, but it seems like --checksum computes the checksum for ALL files, which is time consuming. What would be nice is if we could have a

On 6/30/07, Wayne Davison <wayned@samba.org> committed: > Added Files: > checksum-xattr.diff > Log Message: > A simple patch that lets rsync use cached checksum values stored in > each file's extended attributes. A perl script is provided to create > and update the values. Wayne, You should be aware of two drawbacks of caching checksums in xattrs: First,

Folks: When using rsync to copy huge amounts of data I've found that a significant amount of time is spent computing the checksums. Sometimes hours, ... sometimes days - it depends on the total amount of data checked! And after that sometimes it's only a few files that need to be updated. I've pulled the latest git (rsync-3.1.1pre1) and didn't see anything to address this (or I

https://bugzilla.samba.org/show_bug.cgi?id=12036 Bug ID: 12036 Summary: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

hi! 3 machines all run this same test script. 2 -i386, 1 x-64bit machine. this line: if find / -mount -type f -mtime -1 -print0 | xargs -0 clamscan -l \ $CLAMDAILY $CLAMEXCLUDES -r --no-summary | cut -d: -f1 > $CHANGEDLOG; \ then the $CHANGEDLOG file... on the 32 bit boxes...oh, probably 220 files. On the 64bit box 177,999 files lol (Centos 64bit w/everything installed)! it seems to me

Hi list, I'm a bit worried here. On a server, Centos 4.3 fully-patched SELinux activated, Osiris (a decentralized scanner for files changes on distant servers) signaled me several changes on files who were not (at first sight) affected by a recent update (the list is below). Is there a logic explanation for those changes to happen ? The "rpm -Va" command does not output md5sum

Hi I''m trying to configure bacula''s config file. The issue is everytime the script runs a new key gets generated for bacula. How can I have the config file update only run once with puppet, yet replace the default bacula-fd.conf file. script listed below: class bacula-client { # define which server to use case $datacenter { 1: { $backupserver

Hey all, I''ve open-sources Digg''s apache module: http://github.com/plathrop/puppet-module-apache I know this isn''t much more advanced than what I''ve seen a lot of people using. Here''s my proposition, though. Let''s get all the disparate "apache" modules out there merged together into One Awesome Module. What do you think? One module

https://bugzilla.samba.org/show_bug.cgi?id=13735 --- Comment #3 from Sébastien Béhuret <sbehuret at gmail.com> --- Thank you for suggesting the patches repo. An improved checksum/maybe-checksum algorithm would be great but there appears to be a lot of work to achieve this. Checksums are very handy for special cases (e.g. to detect and fix data corruption) but are still relatively slow and

I am using outgoing call files. I typically see the "ooh something changed / timeout" on a regular bases every second to be exact. Then it stops until some other call event happens. So I "mv" my call file to the outgoing spool directory, I am listening to that message, another call file is "mv"'ed into the directory and something happens to the timeout that its

Hello, I've been testing out 3.0.25 before putting it into production and came across an issue. As a simple example.. in a share definition root preexec = echo "hey there, hi there, hello" > /tmp/hiya.txt works fine under 3.0.24 not so under 3.0.25, /tmp/hiya.txt isn't created. Cranking up the debugging and using some other similiar tests it seems to me that Samba is in

Hi, I have a template file which I would like to append to an existing file (in this case I wish to add a few lines to /etc/motd). Unless I''ve missed it, it does not appear that file has an append option. Is there an easy way copy to the end of a file Thanks Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google

I'm trying to understand the point of the --checksum-seed option. As I understand it from a little reading, checksums are not cached over executions of rsync. So...what is the point of fixing the seed? Is this in support of patches which *do* support caching of checksums? I've read about caching these in files and in xaddr. Is there a "best solution" for caching

Hello, I would like to fit correlation structures with nlme, but R crashes. My data is similar to the "growth of orange trees" example from Pinheiro and Bates (2000), but data are not equally spaced in time, as the last observation is taken after 6 days ( and not 2 as the others). This is the code I'm using: library(nlme)

This is a suggestion for adding to rsync an option "--checksum-path=PROGRAM". Once this option is given, provided it is accompained by option "--checksum", both the receiving and sending side of rsync would compute checksums calling PROGRAM, instead of the usual checksum program. Why is this usefull? Suppose I have two collections of MP3 files at different locations which I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would need to see both your existing rsync command line and the output of --itemize-changes when such an occurrence happens before I can really understand what is happening. In the end, if you have any output at all the bare minimum should be - --itemize-changes. --verbose is utterly useless without it. On 09/07/2015 11:10 PM, Andrej wrote: >

On 8 September 2015 at 13:57, Kevin Korb <kmk at sanitarium.net> wrote: Hi Kevin. > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The ctime will always be newer or the same as the mtime. This is > because changing the mtime also changes the ctime as does other things > like changing the permissions. > > Rsync only pays attention to the mtime because rsync can

Reject Reasons: xcp-xe_1.3-14_amd64.deb: deb contents timestamp check failed [<type 'exceptions.NameError'>: global name 'MTime' is not defined] xcp-squeezed_1.3-14_amd64.deb: deb contents timestamp check failed [<type 'exceptions.NameError'>: global name 'MTime' is not defined] python-xenapi_1.3-14_all.deb: deb contents timestamp check failed [<type

> Thanks Roland. Yes, I didn't even look to verify my fileserver is a DC. I must have debated a few times about the choice and forgot my last decision when installing. I know it's not recommended to run a fileserver on an AD DC, but hopefully you can still offer some advice on troubleshooting. Maybe this isn't even a smb config issue. It could be Windows related??? Here is the

smbclient (and smbtar) in version 2.2.7a (and prior) has problems with large files (> 4GB). The following patch (against 2.2.7a) fixes all known problems with this. This code has been checked into the CVS tree in all branches as well. -- ====================================================================== Herb Lewis Silicon Graphics Networking Engineer