hello i looked in google , faq etc but didnt found a answer. sorry if i overseen something. how i can auth. via a hostkey without make a config in ~/.ssh normaly ssh has support with ssh -i /keyfile is there any way to combine it via rsync , with rsync -e "ssh -i key" ..etc etc does not work thx bye
I had this problem trying to script an unattended backup. (rsync 2.6.1 on cygwin) I found that if you need to pass command line arguments to ssh you need to use: rsync --rsh="ssh -i key" Using -e, if I remember it correctly, just tries to execute a command called "ssh -i key" which, obviously, doesn't exist. I think this is a feature rather than a bug, though. Maybe :) Terry.> hello > i looked in google , faq etc but didnt found a answer. > sorry if i overseen something. > > how i can auth. via a hostkey without make a config in ~/.ssh > normaly ssh has support with ssh -i /keyfile is there any way to combine it > via rsync , with > rsync -e "ssh -i key" ..etc etc does not work > > thx bye >
> rsync -e "ssh -i key" ..etc etc does not workThe best thing you can do is to use -vv to see what command rsync is running and then try a similar command (e.g. use "rsync --help" instead of the server command) to see what is going wrong with your ssh setup. Also, avoid a path that requires shell-expansion (such as ~/key) since the value you specify isn't going to be twiddled by a shell. For example, you might end up runing something like this: ssh -i /path/key remotehost rsync --help As long as that works, you should be able to take the ssh command (without the host) and use it with rsync's -e option. (Aside: -e and --rsh are two aliases for the same option, so they're handled identically inside rsync.) ..wayne..
sc2@gmx.at wrote:> hello > i looked in google , faq etc but didnt found a answer. > sorry if i overseen something. > > how i can auth. via a hostkey without make a config in ~/.ssh > normaly ssh has support with ssh -i /keyfile is there any way to combine it > via rsync , with > rsync -e "ssh -i key" ..etc etc does not work > > thx bye >Have you tried the RSYNC_RSH environment variable yet? -- Aaron W Morris <aaronmorris@mindspring.com> (decep)
I have 2 servers. Both have my home directory on a common file server mounted as /home/wally. I have 2.6.2 in my home directory in /home/wally/rsync/rsync-2.6.2 and I am doing a push from one file server to another. My command line has /home/wally/rsync/rsync-2.6.2/rsync as its command. I have verified that is the command that is in *_rsync_argvs. I had assumed that the remote server would also be using /home/wally/rsync/rsync-2.6.2/rsync for its execution. Could it be simply using "rsync" and using an older "rsync" that happens to be installed and in the path?? The reason I ask is that I am seeing large files being sent twice (not all the times but frequently). This was a bug in 2.5.7 (the native rsync in our redHat distribution). It was reported as being fixed in 2.6.2. I reported it as a "--backup" problem on friday, but over the week end I realized that this may be the old bug and that I noticed it primarily because I was testing "--backup" and that I saw the second copy displacing my backup file. Before I reported that the bug is back, I want to make sure that my environment is doing what I think it is. wally
Thanks Wayne, I did as you suggested and found that the remote system does NOT use /home/wally/rsync/rsync-2.6.2/rsync which is what I had in my Command Line and what was in my xxx.rsync_arvs file. This explained some of the weird behavior I was seeing. I had a 2.6.2 local system working with a 2.5.7 remote system. I have updated all my servers to 2.6.2 and I will rerun my scripts. Hopefully, I will see improved results. wally -----Original Message----- From: Wayne Davison [mailto:wayned@samba.org] Sent: Monday, June 14, 2004 10:20 AM To: Wallace Matthews Cc: rsync@lists.samba.org Subject: Re: question On Mon, Jun 14, 2004 at 09:22:45AM -0400, Wallace Matthews wrote:> Could it be simply using "rsync" and using an older "rsync" that > happens to be installed and in the path??That's the normal case if you don't use the --rsync-path=/PATH/rsync option to tell rsync what program to run. It is easy to determine this for yourself by using -vv (and a nice small transfer) because rsync tells you exactly what command it is running. ..wayne..