On 4 Jan 2002, Mike Li <Mike.Li@schenker.ca> wrote:> Hi Martin, > > Is there a binary for rsync for NCR MP-RAS ver 3.0 running on Intel PIII > Hardware?I've never heard of that. What is it?> I can't seem to be able to compile the source codes either even though I have C > compiler > Here is what I get when I run configure > Thank you in advance > > # ./configure > configure: Configuring rsync 2.5.1 > checking build system type... ./config.guess: unable to guess system > typeHow about ./configure --host=i685-ncr-sysv4.3 This should get rsync going for you.> This script, last modified 2001-07-19, has failed to recognize > the operating system you are using. It is advised that you > download the most up to date version of the config scripts from > > ftp://ftp.gnu.org/pub/gnu/config/ > > If the version you run (./config.guess) is already up to date, please > send the following data and any information you think might be > pertinent to <config-patches@gnu.org> in order to provide the needed > information to handle your system. > > config.guess timestamp = 2001-07-19 > > uname -m = 4400 > uname -r = 4.0 > uname -s = sclback > uname -v = 3.0 > > /usr/bin/uname -p = Pentium III(TM)-ISA/PCI > /bin/uname -X > > hostinfo > /bin/universe > /usr/bin/arch -k > /bin/arch > /usr/bin/oslevel > /usr/convex/getsysinfo > > UNAME_MACHINE = 4400 > UNAME_RELEASE = 4.0 > UNAME_SYSTEM = sclback > UNAME_VERSION = 3.0 > configure: error: cannot guess build type; you must specify one-- Martin linux.conf.au -- Feb 6-9, Brisbane.
On 4 Jan 2002, Mike Li <Mike.Li@schenker.ca> wrote:> ./configure -host=i685-ncr-sysv4.3 > configure: WARNING: If you wanted to set the --build type, don't use --host. > If a cross compiler is detected then cross compile mode will be used. > configure: Configuring rsync 2.5.1 > checking build system type... ./config.guess: unable to guess system > typeWell what about ./configure --build=i685-ncr-sysv4.3 ? -- Martin
I can use -a so far. Why options do not work?
# ./rsync --daemon
rsync: --daemon: unknown option
rsync error: syntax or usage error (code 1) at main.c(793)
# rsync --help
Segmentation Fault - core dumped
Best regards,
Mike Li
Martin Pool
<mbp@samba.or To: Mike.Li@schenker.ca
g> cc:
Subject: Re: rsync for NCR MP-RAS
01/05/02
09:08 PM
Please
respond to
rsync
On 5 Jan 2002, Mike.Li@schenker.ca wrote:>
> Thank you. The compilation worked when I did
> ./configure --build=i686-ncr-sysv4.3 then make
>
> How do I run rsync between target and source servers?
> Do I need to have rsync running on both target and source servers for
> /filesystem_a on target and /filesystem_b on source ?
> I looked at the examples they don't provide what I'm looking for.
Thanks
> again.
Please read the manual and ask on the mailing list if anything is
unclear.
--
Martin
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 me nothing) # ./rsync -a /tmp/ sclback:/tmp/ UX:sh (sh): ERROR: rsync: not found rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(139) # ls -l rsync -rwxr-xr-x 1 root root 313524 Jan 3 10:45 rsync Thank you in advance. Best regards, Mike Li
But 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 I did a rsync --daemon I cannot see an rsync processes when I do a ps -ef | grep rsync # ./rsync -a /tmp/ sclback:/tmp/ UX:sh (sh): ERROR: rsync: not found rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(139) # ls -l rsync -rwxr-xr-x 1 root root 313524 Jan 3 10:45 rsync # cd /usr/local/bin # rsync -a --rsync-path=/usr/local/bin/ /tmp/ sclback:/tmp/ UX:sh (sh): ERROR: /usr/local/bin/: cannot execute rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(139)
On Wed, Jan 09, 2002 at 11:51:00AM -0500, Mike.Li@schenker.ca wrote: ...> # cd /usr/local/bin > # rsync -a --rsync-path=/usr/local/bin/ /tmp/ sclback:/tmp/ > UX:sh (sh): ERROR: /usr/local/bin/: cannot execute > rsync: connection unexpectedly closed (0 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(139) >That hast to be --rsync-path=/usr/local/bin/rsync - Dave
Hi Dave,
It works now. Thanks a lot.
Is there any benchmark comparision of transfer rates between ftp, rcp or
rsync. Thanks again.
Best regards,
Mike Li
Dave Dykstra
<dwd@bell-lab To: Mike.Li@schenker.ca
s.com> cc: rsync@lists.samba.org
Subject: Re: rsync for NCR MP-RAS
01/09/02
12:15 PM
On Wed, Jan 09, 2002 at 11:51:00AM -0500, Mike.Li@schenker.ca wrote:
...> # cd /usr/local/bin
> # rsync -a --rsync-path=/usr/local/bin/ /tmp/ sclback:/tmp/
> UX:sh (sh): ERROR: /usr/local/bin/: cannot execute
> rsync: connection unexpectedly closed (0 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12) at io.c(139)
>
That hast to be --rsync-path=/usr/local/bin/rsync
- Dave
On 9 Jan 2002, Mike.Li@schenker.ca wrote:> > Hi Dave, > It works now. Thanks a lot. > Is there any benchmark comparision of transfer rates between ftp, rcp or > rsync. Thanks again.http://rsync.samba.org/rsync/tech_report/ rsync is most useful if there is already an older version of the file on the destination, in which case it should be much more efficient than the other two. Also, rsync can detect files which need to be transferred based on date stamps, and can compress data in transit. -- Martin