similar to: Rsync like Time Machine

Ok, thank you for this extra info. I have experienced exactly what you described. The rsync dry run is _still_ running after being started at 1:30am PST :) But it is finding the right files to update. Most of the entries are: >fc........ Which is what I want. So, just because I see: >f at the beginning... That doesn't necessarily mean that the file is going to get updated at the

What about -c? It seems I'm getting a lot of spurious file transfer candidates when using: -avvznIi --no-o --no-g --no-p It's showing transfers (receive) for many files I know haven't been tampered with. Thanks, -Clint On Tue, Oct 27, 2015 at 7:53 PM, Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > That is correct.

On Sat Jan 10 2015 at 5:21:33 AM Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > What does --itemize-changes say about that file? Try using the stat > command on the various copies of it to see what is different about them. > In my original message, I stated I used --itemize-changes, and I reported the following: >

When --partial-dir is used rsync creates new or updated files inside a temporary dir. For example the new version of some/path/file is created in some/path/<partial-dir-name>/file and later moved. What happens if a new directory is created? If some/path/newdir/newfile is to be copied, is it done in some/path/<partial-dir-name>/newdir/<partial-dir-name>/newfile? Or is newdir

Hi: I've been using rsync to create backups for a few years. A few months ago I started experiencing sector errors. I ended up replacing the drive and copying the drive data. It turns out that due to the default behavior of rsync "quick check", some of the files were modified without altering the modification time or size, so these files are still clean in the backup. I would like

On Tue, Apr 25, 2017 at 02:41:58PM +0000, Cook, Malcolm wrote: > Might this combination serve the purpose: > * R session keeps an open handle on the tempdir it creates, > * whatever tempdir harvesting cron job the user has be made sensitive enough not to delete open files (including open directories) Good suggestion but doesn't work with the (increasingly popular)

Hi! Usually dovecot auto detects or repairs the size of a maildir message. So I can place a message named "foo" in the cur directory and dovecot uses it. Now I tried the same with a zlib compressed message but here dovecot doesn't recognize/repair the size of the message. When I access this folder via IMAP the connection is diconnected and in dovecot logs I see the following

Hi all. A while ago (April 15th or so) I posted a patch that allows rsync to take multiple --compare-dest or --link-dest arguments, allowing fetching of files not present in multiple trees. I never got any feedback on it, though, so I'm picking it up again. :) Is there any interest in such a patch at all? Below is the usage example i outlined back then; --start-- [...] Its primary usage is

Hi all, I was busy programming a tool to automatically run some tests to update the FLAC comparison page (http://xiph.org/flac/comparison.html) when I stumbled across some weird behaviour of the flac program. So I compiled from git and it seems that this bug still is there. As I don't have any experience on coding C and don't know which bug-report facility to use, this seemed the

rpeng@jhsph.edu wrote: > I get different behavior on Linux: > > system("mkdir newdir") > dir("newdir", all.files = TRUE, recursive = TRUE) ## R hangs The point is that all.files=TRUE implies returning also "." and ".."! Hence the recursion uses to be infinite (from "." to "." to "." ......). If recursiv = TRUE,

Hi Guys, I am new to R and just trying to write a small script to automate a couple commands. But I run into the setwd(): cannot change working directory. I googled a little bit and tried all fixes/suggestions with no success. Basically I have a script that works from inside a directory with my data (/home/sean/Rtest/Data01). Now I want to modify the script to make it run from the upper directory

hei everyone, I have a weird problem: if I do a # cd /somedir; stat somesubdir |grep Modify where /somedir is some directory on an SMB-mounted filesystem I get one datetime... but I I do: # cd /somedir; stat * |grep Modify for the same directory I get a Modify time which consistently differs by 1 second. As I'm writing a perl module to detect differences in a filesystem and rely on the

Do not pass GLOB_MARK as flag for glob(3) in the daemon implementation of glob, so names of directories will not have a trailing slash. This allows users to have filenames that can be used with other tools, such as rm. Add a new test to check this (based on RHBZ#1293271). A mild behaviour change is that users of the glob API now need to append the slash when building paths using its results.

Greetings. If I do this: rsync --hard-links one.server.com::"module/somedir/images/redhat/3.0WS/en/os/i386 module/someotherdir/1.0/images/redhat/3.0WS/en/os/i386" /export/distros I get: /export/distros/i386/... and a conflict between the two sources. I want for destination: /export/distros/images/redhat/3.0WS/en/os/i386 /export/distros/1.0/images/redhat/3.0WS/en/os/i386 In other

Currently, rsync --delete -avvn test1/ test2/ --existing will give output such as: not creating new file "newdir" not creating new file "newdir/newfile" not creating new file "newdir/subdir" It would make more sense if it said: not creating new directory "newdir" not creating new file "newdir/newfile" not creating new directory

Hi, in this thread: https://lists.samba.org/archive/samba/2019-July/224365.html Joachim Lindenberg reminded me that he was using smbclient to sync Sysvol. He posted (in the link above) a link to his original post: https://lists.samba.org/archive/samba/2019-July/224346.html Here he posted a copy of his script. I personally would never have thought about using smbclient, but it just goes to

I'd like to remove automatically a directory that may be non empty. I tried: > file.remove(NewDir, recursive=TRUE) [1] FALSE Warning message: In file.remove(NewDir, recursive = TRUE) : cannot remove file 'Prostate_Validated_mirWalk', reason 'Directory not empty' Is there another command to remove entire directories including their contents ? Thank you. Maura tutti i

Hi: I've been using rsync for a couple years now. Unfortunately, I've made some changes on both ends, so it's unclear what could be the culprit. I make extensive use of --link-dest to provide a cheap "Time Machine"-like backup for a Windows machine. Source: Windows 7 running Cygwin (CYGWIN_NT-6.1 sith 1.7.33-2(0.280/5/3) 2014-11-13 15:47 x86_64 Cygwin) Destination: Synology

On 26/04/2017 4:21 AM, Martin Maechler wrote: >>>>>> <frederik at ofb.net> >>>>>> on Tue, 25 Apr 2017 21:13:59 -0700 writes: > > > On Tue, Apr 25, 2017 at 02:41:58PM +0000, Cook, Malcolm wrote: > >> Might this combination serve the purpose: > >> * R session keeps an open handle on the tempdir it creates, >

I've done quite a bit of looking, but I haven't found an answer that answers this question. Environment: cygwin on Windows rsync 3.0.4 I know that rsync isn't optimzed for speed on local copies - that's clear in my testing. I'm attemting to sync a large volume of files. (In this case, I'm syncing a rdiff-backup set...) An initial sync will be about one fourth as fast a