get working rsync

tim.conway at tim.conway at
Fri Aug 16 08:50:01 EST 2002

It's in your interactive search path.  rsh algsolsrv which rsync, and 
you'll get something like "no biteme in /bin /usr/bin".  rsh is not a 
login session, and thus doesn't run your initialization scripts.
You can probably add the path containing rsync to the global environment, 
but it's be less disruptive to link rsync somewhere in the path, and less 
yet to use the --rsync-path= paramater to just tell rsync which rsync to 
use on the remote end.  That can also guard you against someone sticking a 
different version earlier in your path.

Tim Conway
tim.conway at
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me.... Tim?"

Jozef Gniadek <gniadej at>
Sent by: rsync-admin at
08/16/2002 10:46 AM
Please respond to Jozef Gniadek

        To:     rsync at
        cc:     (bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        get working rsync

I'm new to this list also I'm new to rsync.
I'm looking to get working rsync on my server to synchronize updating
rbl dns table.
For testing, I installed rsync on two sun boxes running solaris 8,
also on those boxes I'm running sshd2 ver.3.1.
Also I setup rshell an both and is working.
rsync is in search path.
When I tried to copy (update) files, I'm getting error messages:

# rsync /inet/gniadej/*.lst algsolsrv:inet/home/gniadej/
ksh: rsync:  not found
unexpected EOF in read_timeout

Probably I'm missing something??..

Any help will be appreciate


Best regards,
 Jozef                          mailto:gniadej at

To unsubscribe or change options:
Before posting, read:

More information about the rsync mailing list