Up until recently, I was running a standard rsync/rsh to rsyncd server combination to sync files. Due to security concerns, I'd like to switch to rsync through ssh. I'm testing with the following from the client side: rsync --verbose --progress --stats --compress --rsh="/usr/local/bin/ssh -p XXXX" \ --recursive --times --perms --copy-links --delete \ /rsynctest/test1 user@SERVER.IP.HERE:"/test1" Rsync connects fine, but then complains it can't find the directory. building file list ... link_stat /rsynctest/test1 : No such file or directory done Number of files: 0 Number of files transferred: 0 Total file size: 0 bytes Total transferred file size: 0 bytes Literal data: 0 bytes Matched data: 0 bytes File list size: 5 Total bytes written: 21 Total bytes read: 16 wrote 21 bytes read 16 bytes 10.57 bytes/sec total size is 0 speedup is 0.00 The directory has been created, the user I'm logging in to ssh through has full permissions on it, but for some reason it won't locate it - do I need to get rid of my old rsyncd.conf or something? I wouldn't think that would affect it... Could it have something to do with the user rsync runs under in rsyncd.conf? Any assistance would be appreciated.
On Sun, Jan 16, 2005 at 04:27:24PM -0700, Aaron wrote:> rsync [...] /rsynctest/test1 user@SERVER.IP.HERE:"/test1" > Rsync connects fine, but then complains it can't find the directory.This is pushing file(s) from /rsynctest/test1 to /test1/test1 on the remote system, so unless that duplication of the "test1" is intended, you'll need to tweak your args a bit. Also, something you said later on in your email made it sound like you were expecting the /rsynctest dir to be on the remote system, and if so, you've got the args mixed up. ..wayne..