freebsdsl at yahoo.com
Fri Apr 23 16:14:01 GMT 2004
However when I first give "rsh 184.108.40.206" and after remote login when i give "which rsync" ; i get the following output
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.
> when i gave "rsh 220.127.116.11 which rsync" at the source system i got the following error
> 18.104.22.168: Connection refused
> "rsh 22.214.171.124" works perfectly fine.
> What could be the problem..?
> Tim Conway wrote:
> rsh 126.96.36.199 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/188.8.131.52
> Tim Conway
> Unix System Administration
> Contractor - IBM Global Services
> conway at us.ibm.com
> opening connection using rsh 184.108.40.206 rsync --server -vvbnlogDtprz .
> 220.127.116.11: 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¢
More information about the rsync