On Fri, Apr 02, 2004 at 09:25:51AM -0500, kenneth topp wrote:
> rsync as server, getting something from a module, the server does a
> pushdir on the backup-dir that the client has. It's required to exist!
I can't duplicate that. What version is the daemon running? What
command are you're runn
You're correct. Here is the where it grabes you:
rsync as server, getting something from a module, the server does a
pushdir on the backup-dir that the client has. It's required to exist!
So not really either, this get's you with new clients to either old or new
servers..
have to dig back in
--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 w
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. Ineffi
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.109&r2=1.110&f=
