Readers, I have tried the following command: rsync -t *.txt ssh user at remote.machine: and receive the following error: rsync: link_stat "local/machinepath/ssh" failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2] My understanding of the manual is that the text files on my local machine should have been transferred to the remote machine. There is one text file, created to practice my use of rsync. What is happening? How do I solve? rsync at conference.jabber.org mandriva 2008 rsync 302
Try rsync -av *.txt:user at remote.machine/path/to/where/you/want/it/to/go/ (assuming you only want to rsync the txt files from the current working directory on the A side - else put the full path in with a trailing slash). Quoting e-letter <inpost at gmail.com>:> Readers, > > I have tried the following command: > > rsync -t *.txt ssh user at remote.machine: > > and receive the following error: > > rsync: link_stat "local/machinepath/ssh" failed: No such file or > directory (2) > rsync error: some files could not be transferred (code 23) at > main.c(1031) [sender=3.0.2] > > My understanding of the manual is that the text files on my local > machine should have been transferred to the remote machine. There is > one text file, created to practice my use of rsync. What is happening? > How do I solve? > > rsync at conference.jabber.org > mandriva 2008 > rsync 302 > -- > Please use reply-all for most replies to avoid omitting the mailing list. > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html > > -- > This email was Anti Virus checked by Astaro Security Gateway. > http://www.astaro.com >
On Mon 17 Aug 2009, e-letter wrote:> > I have tried the following command: > > rsync -t *.txt ssh user at remote.machine: > > and receive the following error: > > rsync: link_stat "local/machinepath/ssh" failed: No such file or directory (2)Does: ssh user at remote.machine actually work to give you a shell on the remote machine? Paul
On Mon 17 Aug 2009, Paul Slootman wrote:> > > > I have tried the following command: > > > > rsync -t *.txt ssh user at remote.machine:Ah, I now see a spurious "ssh" there. That tells rsync that you also want to transfer a file "ssh", in addition to the *.txt files. Do you have a file "ssh" in that directory?> > and receive the following error: > > > > rsync: link_stat "local/machinepath/ssh" failed: No such file or directory (2)Your current working directory is "local/machinepath" ? Paul
On 17/08/2009, simon at tranmeremail.org.uk <simon at tranmeremail.org.uk> wrote:> Try rsync -av *.txt:user at remote.machine/path/to/where/you/want/it/to/go/ > (assuming you only want to rsync the txt files from the current > working directory on the A side - else put the full path in with a > trailing slash).This failed, command terminal response: ssh: *.txt: Name or service not known rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(635) [receiver=3.0.2]
On 17/08/2009, Paul Slootman <paul+rsync at wurtel.net> wrote:> On Mon 17 Aug 2009, e-letter wrote: >> >> I have tried the following command: >> >> rsync -t *.txt ssh user at remote.machine: >> >> and receive the following error: >> >> rsync: link_stat "local/machinepath/ssh" failed: No such file or directory >> (2) > > Does: > ssh user at remote.machine > actually work to give you a shell on the remote machine? >Both ssh user at remote.machine and ssh remote.machine -l user connect successfully.
On 17/08/2009, Paul Slootman <paul at wurtel.net> wrote:> On Mon 17 Aug 2009, Paul Slootman wrote: >> > >> > I have tried the following command: >> > >> > rsync -t *.txt ssh user at remote.machine: >I removed the ssh from the command: rsync -t *.txt user at remote.machine: No response from the command terminal, except for a new prompt: [me at localhost directory]$ I connect to the remote machine in a separate command terminal to see if the text file was transferred and there was no transfer.
On Mon, Aug 17, 2009 at 09:02:42PM +0100, e-letter wrote:> rsync -t *.txt user at remote.machine: > No response from the command terminal, except for a new promptThen it succeeded. If you want it to be more verbose, tell it to be verbose. ..wayne..
On 18/08/2009, Wayne Davison <wayned at samba.org> wrote:> On Mon, Aug 17, 2009 at 09:02:42PM +0100, e-letter wrote: >> rsync -t *.txt user at remote.machine: >> No response from the command terminal, except for a new prompt > > Then it succeeded. If you want it to be more verbose, tell it to be > verbose. >I repeat: I connect to the remote machine in a separate command terminal to see if the text file was transferred and there was no transfer. I repeated the command with the verbose command: rsync -vt *.txt user at remote.machine: sent 39 bytes received 16 bytes 4.40 bytes/sec total size is 24 speedup is 0.44 Again, I connected to the remote machine in a separate command terminal to see if the text file was transferred and there was no transfer.
Tue, 18 Aug 2009 12:53:28 +0100, inpost wrote:> I repeat: I connect to the remote machine in a separate command terminal to see > if the text file was transferred and there was no transfer. > > I repeated the command with the verbose command: > rsync -vt *.txt user at remote.machine: > sent 39 bytes received 16 bytes 4.40 bytes/sec > total size is 24 speedup is 0.44-v will also show the transferred files: so, your shell/rsync did not find any files that * match *.txt, * are in the directory were you called rsync, AND * need to be transferred Sven