similar to: read dir list with write only option

Hi, is rsync supposed to detect permission change only (if other attributes are equal at both source and target)? I'm able to synchronize permissions by -p when the file changes (e.g. its timestamp when -t is used) but otherwise the sole permission change of the file (e.g. via chmod u-w file) remains unnoticed. Any hint? Thanks, Pavel

Hi, I am runing rsync --backup --backup-dir=$BACKUPDIR where the BACKUPDIR=$(date +%d) to recycle the $BACKUPDIR in a month. But rsync does not clean the $BACKUPDIR before writing to it in cycling. I guess you have to clean it manually before the rsync can write to it. As my $BACKUPDIR is in remote machine, do you have to run ssh to delete it first before calling rsync in a script? Or if there

Hi Kevin, Thank you very much for the response. Actually, I don't think I need to clean the backup dir defined in --backup-dir=<backup dir>, when the contents has already been deleted in the destination (no exist), it will delete from the backup dir as well in next cycle, correct? Regards, - j On Thu, Feb 4, 2016 at 12:39 PM, Kevin Korb <kmk at sanitarium.net> wrote: >

with these rsync rsync [...] /var/ /dir/ rsync [...] /etc/ /dir2/ And exclude file: excl /apache2/* That will exclude both /var/apache2/* and /etc/apache2/* How can I tell rsync I want /var/apache2 excluded, but not /etc/apache2? I mean short of using separate excl files for each run Using something like the start of an absolute name:

Kevin Korb <kmk at sanitarium.net> writes: > -/ /var/apache2/* Thanks for the input, but unless I'm doing something else screwy, that does not appear to work here. I put your line verbatim into my exlcude file (near the top) /pkg/* /sadm/* /cache/* /opt/csw/cache/* -/ /var/apache2/* /tmp/* ------- ------- ---=--- ------- ------- My actual task

Cool Thanks! Specifically, the timestamps on both <src> and <dest> match for "ls -l" but do not match for "ls -lu" or "ls -lc” The storage is just an regular HDD in a mac pro tower. I can’t imagine why it wouldn’t handle timestamps. Also of note - this problem doesn’t exist for every file, just the vast majority. So, that just makes it more confusing. Yes,

Hi, On Mon, 13 Apr 2015 12:59:07 -0400 Kevin Korb wrote: > Hmmm, according to my interpretation of the man page (I am on 3.1.1) > that is supposed to work however when I test using the "-/ > /etc/passwd" example the / seems to have the same effect as commenting > the line. I get /etc/passwd copied whether the source is / or /etc. I guess that this -/ syntax is not usable

Dear all is it possible to rsync in a master-slave scenario saving to slave gzip content? i'm not talking about compression during transfer, i'm talking about -saving- the destination in a compressed format. Example: FROM: -folder_A --file_A --file_B TO: -folder_A --file_A.gz --file_B.gz I know that this won't be a "real" rsync between two folder, but it will be an

On Mon, 13 Apr 2015 13:45:18 -0400 Kevin Korb wrote: > The +/- syntax absolutely works in an --exclude-from or --include-from > file I use it all the time. However, apparently the -/ syntax does > not work there. > So, I am not sure if the man page is wrong or if this feature just > isn't working correctly in an exclude file. This is perhaps this note in the "FILTER

Hi, I am running rsync backup on Centos 6, the following command does not seem work, the /backup/fll_copy was fine, but the /backup/Wednesday in the remote machine was not created even I changed the source contents several times. rsync -e "ssh -q -o StrictHostKeyChecking=no" --backup --backup-dir=username at ipaddress:/backup/$(date +%A) -av $SRC username at

On Tue, Mar 20, 2018 at 5:49 PM Kevin Korb <kmk at sanitarium.net> wrote: > Nothing there should be preventing incremental indexing. That means it > should start copying as soon as it finds a file that needs to be copied. > Doesn't it tries to create all (empty) directories first? > On 03/20/2018 02:33 PM, Bráulio Bhavamitra wrote: > > > > > > Em seg, 19

I use --filter='dir-merge .backup-filter" to allow my users to designate portions of their home directories that should be excluded from my rsync-based backup system. I'm looking for a way to periodically generate a report that shows the amount of backup space being used by each user. I've tinkered with writing my own script that processes any filter files into --exclude

OK. Thanks. Where can I find information regarding how to interpret —itemize-changes? The timestamps aren’t changing, so the target must not be storing them, which I have no idea why. The directory I’m writing to is 777. What is the flag to tell rsync to ignore the timestamps? Thanks, Blake On 6/2/16, 6:18 PM, "rsync on behalf of Kevin Korb" <rsync-bounces at lists.samba.org on

Em seg, 19 de mar de 2018 11:34, Kevin Korb via rsync <rsync at lists.samba.org> escreveu: > The performance of rsync with a huge number of files is greatly > determined by every option you are using. So, what is your whole > command line? > rsync -avP /data-old/ /data > > On 03/19/2018 09:05 AM, Bráulio Bhavamitra via rsync wrote: > > Hi all, > > > >

Thank you! I run --times when I use rsync (I actually use the -a flag) but the times do not transfer over and if I run rsync dryrun with -i I can see that it wants to transfer the files because of times. When I run rsync a second time with your suggestion the times do transfer over. I don't know why... B ________________________________________ From: rsync [rsync-bounces at lists.samba.org]

Thanks Kevin! I¹m unclear how to read the ‹itemize-changes output. Can you provide some insight? This is a local transfer from an external drive to an internal drive all attached to one computer. rsync -aPh --itemize-changes -n /Volumes/shuttle_05/2012_79_1_14_1__1199_Workprint /Volumes/3TB_LTO/LT003A/ sending incremental file list >f..t.......

Before anyone yells at me, yes, you can use rsync's --checksum to detect (and fix) files that are incorrect despite having correct timestamps and sizes. This would mean that a previous rsync had been corrupted not the current one. But it is important to note that this would only be reported to you if you also use --itemize-changes and what to look for (a file with a c but not an s or a t).

Hi I am using "rsync" to send files from a source machine to a remote machine as one typically does. I would like to clarify that the "-c" option will cause the checksum on the receiving end to be created by reading the already written file and NOT the data stream on the receiving end. This would help in catching disk I/O errors if the checksum is done on the file on disk.

I am using rsync with --backup --backup-dir to keep copies of files which have changed as part of an incremental backup system. However, if only the timestamp has changed, it creates a copy of the file in --backup-dir, and if thousands of large files have their timestamps changed, this can waste a lot of disk space on something which hasn't really changed. Interestingly, if you use

Hi Kevin, I haven't specified --whole-file. After entering an rsync command the terminal always reads "delta-transmission disabled for local transfer or --whole-file" but I assume that is just a standard phrase that always appears. So, if I am running partial (-P) and not using --whole-file or disabling the delta-transmission, why would an incomplete file be deleted and the