I'm tryng to setup copying some files from one machine to a remote machine in practice of setting up rsync to backup my production server to my backup server. here a copy of what I tried an the error I get. Can someone tell me what im doing worng. jack@dualcpu:/> rsync -a ssh horizon/ root@192.168.0.39:horizon Password: rsync: link_stat "/ssh" failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(791) jack@dualcpu:/> when I get the Password: line i type in the root password for the remote machine. When I get this going I plan to set this up on another machine but right now trying it out on my test bed machine. thanks jack
Hey Jack,
You need to add -e in front of ssh. So try this:
rsync -a -e ssh horizon/ root@192.168.0.39:horizon
Cheers,
Nick
On 10/19/05, Jack Malone
I'm tryng to setup copying some files from one machine to a remote machine in practice of setting up rsync to backup my production server to my backup server. here a copy of what I tried an the error I get. Can someone tell me what im doing worng.
jack@dualcpu:/> rsync -a ssh horizon/ root@192.168.0.39:horizon Password: rsync: link_stat "/ssh" failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(791) jack@dualcpu:/>
when I get the Password: line i type in the root password for the remote machine.
When I get this going I plan to set this up on another machine but right now trying it out on my test bed machine.
thanks jack
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Nick
On Wednesday 19 October 2005 03:06 pm, Nick Vahalik wrote:
Hey Jack,
You need to add -e in front of ssh. So try this:
rsync -a -e ssh horizon/ root@192.168.0.39:horizon
Also add a slash after the last 'horizon'. Rsync is very particular about slashes. Ok done that but get nuthing copied to the remote machine. so I added the v (verbose) flag too so that rsync tells me what it's doing, an I get
At 02:11 PM 10/19/2005, Bruce Marshall wrote: the following error message jack@dualcpu:/> rsync -a -e -v ssh horizon/ root@192.168.0.39:horizon/ rsync: Failed to exec -v: No such file or directory (2) rsync error: error in IPC code (code 14) at pipe.c(83) rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1099) Thanks for the quick replies nick an bruce. jack
Jack,
-e needs to be followed by ssh
rsync -a -e ssh -v ...
Whatever follows -e is what transport program gets executed on the remote
system.
Cheers,
Nick
On 10/19/05, Jack Malone
On Wednesday 19 October 2005 03:06 pm, Nick Vahalik wrote:
Hey Jack,
You need to add -e in front of ssh. So try this:
rsync -a -e ssh horizon/ root@192.168.0.39:horizon
Also add a slash after the last 'horizon'. Rsync is very particular about slashes. Ok done that but get nuthing copied to the remote machine. so I added the v (verbose) flag too so that rsync tells me what it's doing, an I get
At 02:11 PM 10/19/2005, Bruce Marshall wrote: the following error message
jack@dualcpu:/> rsync -a -e -v ssh horizon/ root@192.168.0.39:horizon/ rsync: Failed to exec -v: No such file or directory (2) rsync error: error in IPC code (code 14) at pipe.c(83) rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1099)
Thanks for the quick replies nick an bruce.
jack
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Nick
On Wednesday 19 October 2005 03:16 pm, Jack Malone wrote:
jack@dualcpu:/> rsync -a -e -v ssh horizon/ root@192.168.0.39:horizon/ rsync: Failed to exec -v: No such file or directory (2) rsync error: error in IPC code (code 14) at pipe.c(83) rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1099)
no, no, no Here is my standard command that I use for almost anything: rsync -auvzr -e ssh frommachine:/mydirectory/ tomachine:/mydirectory/ where I usually only have one of the <> parms..... The -e *has* to go with the ssh. You spearated it.
----- Original Message -----
From: "Bruce Marshall"
On Wednesday 19 October 2005 03:16 pm, Jack Malone wrote:
jack@dualcpu:/> rsync -a -e -v ssh horizon/ root@192.168.0.39:horizon/ rsync: Failed to exec -v: No such file or directory (2) rsync error: error in IPC code (code 14) at pipe.c(83) rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1099)
no, no, no
Here is my standard command that I use for almost anything:
rsync -auvzr -e ssh frommachine:/mydirectory/ tomachine:/mydirectory/
where I usually only have one of the <> parms.....
The -e *has* to go with the ssh. You spearated it.
Correct, But for the record, there is no need for the 'r' if you are using 'a' because: -a, --archive archive mode, equivalent to -rlptgoD As to whether you need the directory/ or just directory, think of it this way: The ending "/" tells rsync to copy everything *within* the directory but not the directory itself. If omitted, rsync copies the directory itself. For backup purposes, I usually find it simpler to *not* use a trailing "/" and to allow rsync to copy the directory to the backup location. -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com --
On Wed, 2005-10-19 at 15:11 -0400, Bruce Marshall wrote:
On Wednesday 19 October 2005 03:06 pm, Nick Vahalik wrote:
Hey Jack,
You need to add -e in front of ssh. So try this:
rsync -a -e ssh horizon/ root@192.168.0.39:horizon
Also add a slash after the last 'horizon'. Rsync is very particular about slashes.
Not needed on the destination but required on the source. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Wed, 2005-10-19 at 16:59 -0400, Ken Schneider wrote:
On Wed, 2005-10-19 at 15:11 -0400, Bruce Marshall wrote:
On Wednesday 19 October 2005 03:06 pm, Nick Vahalik wrote:
Hey Jack,
You need to add -e in front of ssh. So try this:
rsync -a -e ssh horizon/ root@192.168.0.39:horizon
Also add a slash after the last 'horizon'. Rsync is very particular about slashes.
Not needed on the destination but required on the source.
Required is a little strong, highly recommended. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Wed, 2005-10-19 at 17:05 -0400, Ken Schneider wrote:
On Wed, 2005-10-19 at 16:59 -0400, Ken Schneider wrote:
On Wed, 2005-10-19 at 15:11 -0400, Bruce Marshall wrote:
On Wednesday 19 October 2005 03:06 pm, Nick Vahalik wrote:
Hey Jack,
You need to add -e in front of ssh. So try this:
rsync -a -e ssh horizon/ root@192.168.0.39:horizon
Also add a slash after the last 'horizon'. Rsync is very particular about slashes.
Not needed on the destination but required on the source.
Required is a little strong, highly recommended.
A trailing slash on the source changes this behavior to avoid creating an additional directory level at the destination. You can think of a trailing / on a source as meaning "copy the contents of this directory" as opposed to "copy the directory by name", but in both cases the attributes of the containing directory are transferred to the contain‐ ing directory on the destination. In other words, each of the follow‐ ing commands copies the files in the same way, including their setting of the attributes of /dest/foo: rsync -av /src/foo /dest rsync -av /src/foo/ /dest/foo are both the same. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
participants (5)
-
Bruce Marshall -
david rankin -
Jack Malone -
Ken Schneider -
Nick Vahalik