On Thursday 3 Jan 02, Itzkovich, Shraga writes:
Cygwin1.dll was copied from the NT4 rsync folder to windows 2000 system32
folder.
Uggh. That's a bad idea if you ever want to use Cygwin for anything
else besides rsync.
David
(Cygwin FAQ maintainer)
I still have problems running the options
like /usr/local/bin/rsync --daemon
will give me an error
Thanks in advance.
# ./configure -build=i686-ncr-sysv4.3
# make install
mkdir -p /usr/local/bin
./install-sh -c -m 755 rsync /usr/local/bin
mkdir -p /usr/local/man/man1
Wow, that's a new one. It's quite surprising that that would cause the
symptoms you described, but I think I can imagine how. The remote end
would ignore the -e ssh, but it's possible that the -ax could result in
different information being passed back and forth after the large file is
sent if
On Sun, Jan 06, 2002 at 05:58:46PM -0600, John E. Malmberg wrote:
The following popt files need patches in order to compile using Compaq C
on OpenVMS. These patches should also be needed on a Tru64 or LINUX on
ALPHA using Compaq C. Except for the alloca issue, these should work on
any
On Mon, Jan 07, 2002 at 12:27:55PM -0500, Hunter French wrote:
I am having problems with Rsync running between 2 FreeBSD computers. We
are trying to use it to backup a directory on the primary server
/var/mail (using a pull method). The configuration on the primary
server (Polaris) should
Probably, but that just means that there was an addtional bug in the
original code.
At this phase, I am just trying to get rid of the compiler diagnostics
with out changing what the code is intending on doing.
Right now I am trying to make sense of what char declarations should
really be
