similar to: rsync: on remote machine: --time-limit=4: unknown option

We've been using RSYNC to back things up and it's sick nasty wicked awesome. Recently we migrated our receiving server to a different machine (Debian lenny) and now we're running into this DROP-CACHE: UNKNOWN OPTION error: sender-machine$ *rsync -Cvaz -e ssh --delete --exclude blah/ --exclude yadda/ . user at receiver:/path/for/drop* rsync: on remote machine: --drop-cache: unknown

I'm trying to sync from 3.0.5 to 2.5.5 (SCO, *sigh*) The source machine errors out b/c the --remove-source-files (or --remove-sent-files) options don't exist on 2.5.5. But, since these option are only acted on by the sending machine (which is where I'm typing the command line), it would be so nice if the source machine would NOT pass the option on to the receiver (or at least, not

Hello all, I'm using R to visualize and explore the data produced by a software system. The software generates logs for many types of events. The software runs for days on end, and can possibly generate multiple events per second. What is the appropriate time format for year, month, day, hour, minute, second, millisecond? that R can properly interpret (using zoo? or ITS?) I'll have

Can anyone let me know how to make the timestamp of the file as that of the remote machine after rsync.

Hello all, I'm getting much further with my time-series work, but still getting into some problems. I'm using POSIXct time format with both date and time. I'd like to use that in an its object but It seems its only processes the date part of the POSIX time stamps: BMU_its_data <- its(data[BMUindex,2-4],dates=data[BMUindex,1]) Error in `row.names<-.data.frame`(`*tmp*`,

Hi, I read below lines in rsync v3.0.5 for --relative option. if you used this command: rsync -av /foo/bar/baz.c remote:/tmp/ ... this would create a file named baz.c in /tmp/ on the remote machine. If instead you used rsync -avR /foo/bar/baz.c remote:/tmp/ then a file named /tmp/foo/bar/baz.c would be created on the remote machine, preserving its full path It is also possible to limit the

I am trying to run: rsync --dry-run -avz --force --no-whole-file -e "ssh -C" --delete --bwlimit=35 \ --backup --exclude "*.backup-*" --exclude "*:*" '--suffix'=.backup-`date +%m%d` \ /mnt/unite-c/ heraudet@nanardon.zarb.org:~/unite-c/ But I get: rsync: on remote machine: --suffix-dels=.backup-0206: unknown option rsync error: syntax or

Hello, I asked the below back at the beginning of August but have received no replies. If anyone can help me with this problem it would be much appreciated. If I have not provided some necessary information then please let me know so I may do so. Thanks in advance. > I have been working on a backup server where I have a server-side script > that wraps the server-side rsync invocation. I

If you want to pass non-rsync args (etc) you should be using --rsync-path. The -M option is only for sending rsync-related options. ..wayne.. On Fri, Oct 28, 2016 at 7:32 AM, John Lane <rsync at jelmail.com> wrote: > > Hello, I asked the below back at the beginning of August but have > received no replies. If anyone can help me with this problem it would be > much appreciated.

Hi there, I use rsync to push files from remote servers. I added "run-time" patch to stop running at 8 am. If run goes to 8am, I should received a "run-time limit exceeded" error. But, half the time, I get : rsync: [sender] write error: Broken pipe (32) rsync error: timeout in data send/receive (code 30) at io.c(829) [sender=3.1.1] == Error at 08:00:15 == I passed

hi, i'm using machine 1 (SuSE 9.0 32Bit): rsync 2.6.2 (from SuSE RPM) machine 2 (SuSE 9.1 64Bit): rsync 2.6.2 (from SuSE RPM) my command looks like the following: /usr/bin/rsync -W --progress --rsync-path=/usr/local/bin/rsync -e ssh --delete --force -av /data/ machine2:/data/machine1/ after rsyncing both machines, some files differ ! i verified these differences with "diff",

Hi, I hacked rsync version 2.6.0 to support a file size limit. I did this, because I could not find a way to do this with the existing rsync options. I've been receiving the rsync digest for several months, and habe not seen mention of this type of feature., This allows rsync to 'prune' out LARGE files when doing the sync. I've been using this for about a month now to provide

I have been working on a backup server where I have a server-side script that wraps the server-side rsync invocation. I have used the client-side rsync -M (--remote-option) to send options to the server script, removing them from the command-line prior to invoking the server-side rsync. This was discussed on Stack Exchange (http://unix.stackexchange.com/questions/297143). It works well. However,

https://bugzilla.samba.org/show_bug.cgi?id=8375 Summary: rsync with bandwidth limit sometimes expend extra time Product: rsync Version: 3.0.8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: fbmoser at

All, Sometimes when I do an rsync, it times out and leaves on orphaned process on the remote machine. I am running rsync over ssh using public key authentication. I synchronize about twenty-five machines, and this problem only appears on one of them. It worked until recently on this machine. I don't know what changed or what is different. I run rsync with a command line like this

sh-3.2# /Users/andre/Desktop/Skripte/rsync_tm Kopiere Time Machine Backup ... rsync: chgrp "/Volumes/G-DRIVE Thunderbolt 3/Backups.backupdb/.RecoverySets/0/com.apple.recovery.boot/boot.efi" failed: Operation not permitted (1) rsync: failed to set times on "/Volumes/G-DRIVE Thunderbolt 3/Backups.backupdb/iMac": Operation not permitted (1) rsync: symlink "/Volumes/G-DRIVE

I updated to 2.3.0 today, and now I'm getting these entries in my log: Jul 7 14:26:20 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17687 + ident lmtp/backup at backup.invalid Jul 7 14:26:20 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup at backup.invalid Jul 7 14:26:21 mail-cbf dovecot: anvil: Error:

Hi I'd like to rsync a large amount of data over a slow connection, but only during night hours. I couldn't find a parameter that limits the time that rsync is running, only the timeout on idle time. I guess the way to go would be to start rsync, get the process ID and kill the process later on. Has anybody already written a bash script that would do something like that? Are there other

I've been very interested in these discussions and uses of rsync as a "clone" of Time Machine. A couple of things have been keeping me from a fully automated solution. I'd like to eliminate the need for Samba/NFS mounts of any kind, because they have proven to be unreliable for me and under some operating environments (Cygwin) it breaks --link-dest. In most of the articles

Time Machine will enable ownership on the drive the first time it starts up. The first thing it does when it creates the backup directory is to enable ownership on the drive. I've seen this happen repeatedly (it's actually the easiest way I know of to enable ownership on drive). On 2018-04-03, at 4:05 AM, Dave Gordon via rsync <rsync at lists.samba.org> wrote: > On 20/03/18