RE: rsync: push_dir TESTDIR: No such file or directory

I'm glad it's working. I wonder what was going on on the destination that could be fixed with a reboot... but on a production environment, sometimes root cause analysis is a luxury you just can't afford. Too true. Luckily, this is my own home machine, so I can do all the poking I need

RE: rsync: push_dir TESTDIR: No such file or directory

Daemian: You're mixing two mutually-exclusive modes - rsync over ssh, and rsync over rsync internal TCP transport to an rsyncd. -e ssh is ignored on rsync to rsyncd, and rsync to rsyncd requires the double-colon(::) representation of the remote. The --port= is also relevant only

rsync: push_dir TESTDIR: No such file or directory

Hi all. I'm getting the following error when using rsync: nice -n 20 rsync -e ssh -p3 --recursive --verbose --verbose --checksum --times --modify-window 2 --port=31000 --dry-run /cygdrive/f/bkp/Doc/Builds/Buildsheets/ [EMAIL PROTECTED]:TESTDIR opening connection using ssh -p3 -l

RE: rsync: push_dir TESTDIR: No such file or directory

Hi all. I'm getting the following error when using rsync: nice -n 20 rsync -e ssh -p3 --recursive --verbose --verbose --checksum --times --modify-window 2 --port=31000 --dry-run /cygdrive/f/bkp/Doc/Builds/Buildsheets/ [EMAIL PROTECTED]:TESTDIR In case this helps clarify the issue

STDERR vs STDOUT?

Hi all. I'm writing an installation script that uses Cygwin's bash.exe to launch an rsync.exe process, which is passed arguments. This performs an rsync over the Internet. I'd like to capture stdout to one file, and stderr to another, so that I can have a clean log of any errors. However,

RE: No --delete-after?

On Fri, Dec 21, 2001 at 04:05:01PM -0500, Mack, Daemian wrote: I can get --delete to work, but I'd prefer to delete files only on a successful transfer, to ensure that the end-user has a working collection of files, no matter what release. For some reason, --delete-after does nothing

No --delete-after?

Is anyone successfully using the Cygwin rsync on Win2k (or NT4) as both daemon and client, with --delete-after working on the client? I can get --delete to work, but I'd prefer to delete files only on a successful transfer, to ensure that the end-user has a working collection of files, no matter

RE: rsync *Still* Copying All Files?

Try --modify-window 2. I'm not sure that will work because it sounds like you're copying between two filesystem types that are the same, but the option was added to copy between PC filesystems that have a timestamp granularity of 2 seconds and Unix filesystems that have a granularity