You need to use a --rsync-path option pointing to where the binary is on
the remote machine, or make sure rsync is in the default PATH for the
remote shell.
- Dave Dykstra
On Tue, Jan 08, 2002 at 02:18:40PM -0500, [EMAIL PROTECTED] wrote:
>
> I'm using the binaries for rsync-2.5.1.SVR42.i386.ta
I'm using the binaries for rsync-2.5.1.SVR42.i386.tar
I still have some usage issues when I try to rsync /tmp from local server
to /tmp on remote server (sclback). Pls advise. Thanks.
on Remote server (sclback) I did a rsync --daemon (I can't see any daemon's
running as ps -ef | grep rsync return
Compiled rsync 2.5.1 using gcc version 3.0; warnings but no errors after
defining HAVE_SNPRINTF HAVE_VSNPRINTF, HAVE_C99_VSNPRINTF in lib/snprintf.c
(otherwise make dies while compiling snprintf.c complaining of snprintf being
re-defined). I had been hoping this version of rsync would allow the
On Tue, Jan 08, 2002 at 10:15:14AM +0100, [EMAIL PROTECTED] wrote:
> Hello,
>
> to explain:
> I have two machines running the same hard- and software.
> Each has two harddrives 80GB/40GB with 500 megs of RAM and
> a 650MHz PIII, running SuSE Linux 7.1 with Kernel 2.2.18.
>
> They are connecte
Hello,
to explain:
I have two machines running the same hard- and software.
Each has two harddrives 80GB/40GB with 500 megs of RAM and
a 650MHz PIII, running SuSE Linux 7.1 with Kernel 2.2.18.
They are connected on a local 100Mbps Ethernet.
The harddrives are pretty full (total ~94GB) with a
