Hi.
I've got 2 Fedora Linux (a Master and a Slave) with RSYNC-2.5.7. I need to keep Master synchronized
every 5 minutes (mounting a remote directory with NFS on Slave).
It runs correctly.
To simulate a problem, I try to disconnect the lan cable.
From the shell of Slave:
rsync -a -v
With this patch (see URL), backup-dir is passed to the server. It's not
currently ignored on the other end if irrelevant (which it is for
senders). Either we should not pass it, or let the sender ignore it
later on.
http://cvs.samba.org/cgi-bin/cvsweb/rsync/options.c.diff?r1=1.109r2=1.110f=h
Hi,
Hope this is the right address.
We are working on a new script that will save possibly hundreds of MBs
in bandwith using rsync.
As you know, having to download hundreds of complete files because the
last part of the file name has changed ( eg. XFree-17 is now XFree-18)
is a waste
Hi all,
I just ran into a problem with rsync-2.6.0. Communication is
between two Linux hosts. One host boots, detects the first, runs
rsync to copy all data, and then shuts down again (to have a
backup for the main server).
In the environment during boot, in which rsync is running in
client
On Tue, Mar 30, 2004 at 09:33:26AM +0200, Francis Montagnac wrote:
On Fri, Mar 26, 2004 at 08:55:48PM -0600, John Van Essen wrote:
Example cmd: rsync -a --relative /home/me /dest
Source root: /home
I think it's instead:
Source root: /
Am i wrong?
I think you're right. Elsewhere in
On Wed, Mar 31, 2004 at 08:19:02AM -0500, kenneth topp wrote:
With this patch (see URL), backup-dir is passed to the server.
Yeah, that change did get made in 2.6.0 (though I don't currently
remember exactly why).
Regardless, you weren't entirely clear what prompted you to mention
this.
On Wed, Mar 31, 2004 at 09:39:17AM -0600, Wolfgang Oertl wrote:
The client therefore doesn't send anything, and both server and client
wait forever.
Yeah, that's not a good failure condition. I've changed the code to
use a default username of guest if neither USER nor LOGNAME is defined
in the
--On Wednesday, March 31, 2004 8:58 AM -0800 Wayne Davison
[EMAIL PROTECTED] wrote:
Regardless, you weren't entirely clear what prompted you to mention
this. Inefficiency? Or a compatibility bug?
In thinking about multi-version compatibility, it seems to me that if a
2.5.x client/receiver
On Wed, Mar 31, 2004 at 07:55:01AM -0800, Wayne Davison wrote:
I wonder if we should change the examples to have multiple sources?
Perhaps this would be good:
Let's say that we want to match two source files, one with an absolute
path of /home/me/foo/bar, and one with a path of
On Wed 31 Mar 2004, Wayne Davison wrote:
On Wed, Mar 31, 2004 at 09:39:17AM -0600, Wolfgang Oertl wrote:
The client therefore doesn't send anything, and both server and client
wait forever.
Yeah, that's not a good failure condition. I've changed the code to
use a default username of
Date: Wed Mar 31 17:02:22 2004
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv27543
Modified Files:
options.c
Log Message:
Don't complain about a null --suffix if we're the server/sender (since
we might not have received the --backup-dir path from the
Date: Wed Mar 31 18:52:38 2004
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv15022
Modified Files:
authenticate.c
Log Message:
The auth_client function must not return without outputting something
on the socket, so a NULL or empty username now
Date: Wed Mar 31 18:53:58 2004
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv15075
Modified Files:
rsync.yo
Log Message:
Improved the include/exclude example section some more. Document
the new username default of guest if neither USER or LOGNAME is
13 matches
Mail list logo
