Rsync Error..

[Naveen Babu]

However when I first give "rsh 66.123.34.123" and after remote login when i give "which rsync" ;  i get the following output 
/usr/local/bin/rsync.
 


Jim Salter <jim at jrssystems.net> wrote:
Clearly, if you can't execute the "which" command remotely, rsh is _not_ 
working "perfectly fine." If you can't use it for remote command 
execution, it isn't going to serve as an rsync transport.

Jim Salter
JRS Systems

> Hello,
> when i gave "rsh 66.123.34.123 which rsync" at the source system i got the following error
> 66.123.34.123: Connection refused
> 
> "rsh 66.123.34.123" works perfectly fine.
> 
> What could be the problem..?
> 
> Thanks,
> Naveen.
> 
> Tim Conway wrote:
> rsh 66.123.34.123 which rsync
> I expect you'll get something like "no rsync in /usr/bin /usr/ccs/bin 
> /usr/bin/X11 /usr/contrib/bin /usr/local/bin ." Some systems don't report 
> the remote shell connection open until the called remote program comes up, 
> so one missing from the path can look like a network timeout. I don't 
> remember if that's true of any FreeBSD.
> If this is the case, use --rsync-path=/wherever/it/is/on/66.123.34.123
> 
> Tim Conway
> Unix System Administration
> Contractor - IBM Global Services
> desk:3032734776
> conway at us.ibm.com
> 
> 
> opening connection using rsh 66.123.34.123 rsync --server -vvbnlogDtprz . 
> /destinationpath
> 66.123.34.123: operation timed out
> rsync: connection unexpectedly closed (0 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12) at io.c(189)

		
---------------------------------
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢