On Thu 29 Apr 2004, Ryan Holowaychuk wrote:
>
> I am getting the following error
>
> [EMAIL PROTECTED] etc]# rsync 192.168.100.25::backup
You're missing the local target (or source, depending on what you were
trying to do).
> rsync: failed to connect to 192.168.100.25: Connection refused rsync
At least it does for me on v5.1
It is a result of a bug in sh on OSF1.
"$var"? doesn't do file-globbing if $var contains a / (it does if it
doesn't). This causes a touch command in teh merge test to fail.
WORKAROUND:
Set BIN_SH=xpg4 in your environment while running the test. Thi
The large file support in configure tests for working file-locking.
This may fail if you are building over NFS and the NFS locking isn't
working.
rsync doesn't actually use file-locking, so this test causes it to
remove large-file support unnecessarily.
A workaround might be to bui
Hi,
I just tried to compile rsync-2.6.2pre1 under AIX 4.3 (gcc 2.95.3) and got
the following compiler error:
gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c clientname.c
-o clientname.o
clientname.c: In function `client_name':
clientname.c:121: `AI_NUMERICHOST' undeclared (first
On Fri, Apr 30, 2004 at 03:30:45PM +0200, Jens Schleusener wrote:
> #ifdef AI_NUMERICHOST
>hints.ai_flags = AI_NUMERICHOST;
> #endif
Thanks, I've added the #ifdef as you suggested.
..wayne..
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting,
On Fri, Apr 30, 2004 at 11:45:47AM +0100, Gordon Lack wrote:
> rsync doesn't actually use file-locking, so this test causes it to
> remove large-file support unnecessarily.
Rsync uses range-locking in its daemon code to implement the
"max connections" option.
> A workaround might be to build on a
On Fri, Apr 30, 2004 at 11:22:37AM +0100, Gordon Lack wrote:
>"$var"? doesn't do file-globbing if $var contains a / (it does if it
> doesn't).
I've tweaked the merge test to not rely on the shell's file-globbing to
get things done. Thanks for the report,
..wayne..
--
To unsubscribe or chan
On Thu, Apr 29, 2004 at 05:00:32PM -0400, Chris Shoemaker wrote:
> Instead of any update, with the --write-batch=mytest argument, rsync just hangs.
The batch code is still experimental (as noted in the man page), so I'm
not surprised by this. The code still needs someone to test it and fix
it to
Rsync version 2.6.2 has been released. It is a bugfix release that
mainly fixes a bug with the --relative option (-R) in 2.6.1 that could
cause files to be transferred incorrectly. This only affected a source
right at the root of the filesystem, such as "/" or "/*" (using "." as
the source after a
Does the --backup, --backup-dir set require that either then source or
target be a remote connection?
Test folder hierarchy:
/Users/localskaiser/source/myfile.txt
/Users/localskaiser/source/a/b/c/newfile.txt
/Users/localskaiser/target
/Users/localskaiser/archive
I can not get the following comm
On Fri, Apr 30, 2004 at 04:19:35PM -0400, Sean M. Kaiser wrote:
> [skaiser-pbg4:~] localska% /usr/local/bin/rsync --delete --backup
> --backup-dir=/Users/localskaiser/archive -a /Users/localskaiser/source
> /Users/localskaiser/target
This command works fine for me when used as you described.
> st
Hi,
What would happen if two people ran rsync on the same set of source
files to the same destination machine? Do we need some sort of
queuing or interlock mechanism to prevent simultaneous rsyncs?
We have a script that uses rsync to distribute files from our AFS
space here to the local disks
12 matches
Mail list logo
