Re: ssh failure due to local error

2009-08-19 Thread e-letter
The local folder contained the text file, which was confirmed by the command ls ./ When I go to the remote machine and repeat this command, the file is not shown which means that transfer failed. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change

Re: ssh failure due to local error

2009-08-18 Thread e-letter
On 18/08/2009, Wayne Davison way...@samba.org wrote: On Mon, Aug 17, 2009 at 09:02:42PM +0100, e-letter wrote: rsync -t *.txt u...@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

Re: ssh failure due to local error

2009-08-18 Thread Sven Hartrumpf
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 u...@remote.machine: sent 39 bytes

ssh failure due to local error

2009-08-17 Thread e-letter
Readers, I have tried the following command: rsync -t *.txt ssh u...@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

Re: ssh failure due to local error

2009-08-17 Thread simon
Try rsync -av *.txt:u...@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 inp...@gmail.com: Readers, I have tried the

Re: ssh failure due to local error

2009-08-17 Thread Paul Slootman
On Mon 17 Aug 2009, e-letter wrote: I have tried the following command: rsync -t *.txt ssh u...@remote.machine: and receive the following error: rsync: link_stat local/machinepath/ssh failed: No such file or directory (2) Does: ssh u...@remote.machine actually work to give you a

Re: ssh failure due to local error

2009-08-17 Thread Paul Slootman
On Mon 17 Aug 2009, Paul Slootman wrote: I have tried the following command: rsync -t *.txt ssh u...@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?

Re: ssh failure due to local error

2009-08-17 Thread e-letter
On 17/08/2009, si...@tranmeremail.org.uk si...@tranmeremail.org.uk wrote: Try rsync -av *.txt:u...@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).

Re: ssh failure due to local error

2009-08-17 Thread e-letter
On 17/08/2009, Paul Slootman paul+rs...@wurtel.net wrote: On Mon 17 Aug 2009, e-letter wrote: I have tried the following command: rsync -t *.txt ssh u...@remote.machine: and receive the following error: rsync: link_stat local/machinepath/ssh failed: No such file or directory (2) Does:

Re: ssh failure due to local error

2009-08-17 Thread e-letter
On 17/08/2009, Paul Slootman p...@wurtel.net wrote: On Mon 17 Aug 2009, Paul Slootman wrote: I have tried the following command: rsync -t *.txt ssh u...@remote.machine: I removed the ssh from the command: rsync -t *.txt u...@remote.machine: No response from the command terminal, except