Rsh only sets up a limited path for you. Do the command:
rsh remote_host echo \$PATH
(or ssh remote_host echo \$PATH)
and this will tell you what your remote PATH is. Perhaps install rsync into
one of these directories or use sym links. If you are using ssh have a look
at the man page about cha
Title: What is the invocation of rsync on the other side?
Folks,
Exactly how is rsync invoked on the remote end, assuming you have
a command line like this?
rsync --archive --recursive --update --links --sparse \
--rsh='ssh -2' --delete --compress backup@host:/src /dest
The reason I as
Excellent! Thanks! You solved my problem, maybe I can solve yours. If
you have root access on the remote server, try linking from /usr/bin/rsync
to /usr/local/bin/rsync. Here's the command:
ln -s /usr/local/bin/rsync /usr/bin/rsync
Now, can someone tell us why the remote shell isn't seeing /
I just got done dealing with this problem.
It was solved for me using the
--rsync-path=/usr/local/bin/rsync
flag, specifying the remote location of rsync.
It be great if someone knew how to avoid using
this parameter.
cheers,
Dave
- Original Message -
From: "Bob Foster" <[EMAIL PROT
Hi,
When I rsync to one of my servers, after I enter the password, I get the
following:
bash: rsync: command not found
unexpected EOF in read_timeout
I can ssh to and from this server. I can rsync from it. Any ideas?
Thanks!
Bob Foster
On Thu, May 17, 2001 at 04:43:50PM -0400, Jim Ogilvie wrote:
> Hi,
>
> I know rsync creates temp files in the destination directory and
> then at some point renames them to the original file name. Therefore
> the destination directories need to be larger than the source directories.
>
> I'm tr
In message <[EMAIL PROTECTED] >, "Jim Ogi
lvie" writes:
> Hi,
>
> I know rsync creates temp files in the destination directory and
> then at some point renames them to the original file name. Therefore
> the destination directories need to be larger than the source directories.
>
> I'm trying
Hi,
I know rsync creates temp files in the destination directory and
then at some point renames them to the original file name. Therefore
the destination directories need to be larger than the source directories.
I'm trying to find a way to calculate how much larger the destination
directories
On 16 May 2001 20:49:10 +0100, bernard.mcauley wrote:
> Hi,
>
> I'm currently using rsync to mirror a large directory at a remote site.
> The directory tree is over 40 GB in size and undergoes constant updates.
> However, I would like to have more control over the mirror as changes to
> the dire
