le. I figured I'd ask about the underlying logic
before attempting a patch.)
Thanks --
JD Paul
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsyn
On Tue, 18 Dec 2001, Martin Pool wrote:
> On 4 Dec 2001, JD Paul <[EMAIL PROTECTED]> wrote:
> > Here's a new version of my rsync-server-over-remote-shell patch:
>
> This looks good. My main reservation is that it makes it even harder
> to explain how rsync works
way for the client to do
anything to the environment, and it should be safe.
Cheers --
JD Paul
[EMAIL PROTECTED]
P.S. Question -- is the enum { } of all the OPT_ variables in
options.c necessary any more? It loo
Actually, my patch already has that in rsync_module():
if (is_a_socket(f_in)) {
addr = client_addr(f_in);
host = client_name(f_in);
} else {
char *ssh_client = getenv("SSH_CLIENT");
addr = ssh_client ? ssh_client : "n
Hi --
Sorry for the delay getting back to you; Thanksgiving holiday
intervened and I'm only now catching up on my email backlog
1. You're entirely right about the --remote-user option. I'll remove that.
2. I'll merge with the latest version from CVS.
3. I'll do that; I prefer -u myself.
>
dest
Cheers --
JD
[EMAIL PROTECTED]
On Tue, 20 Nov 2001, JD Paul wrote:
> On Tue, 20 Nov 2001, Dave Dykstra wrote:
>
> > I'm uncomfortable with adding yet another syntax. I'd prefer just keyin
On Tue, 20 Nov 2001, Dave Dykstra wrote:
> > rsync [options] -e ssh source [...] [user@]host:::module[/path]
> > rsync [options] -e ssh [user@]host:::module[/path] dest
>
> I'm uncomfortable with adding yet another syntax. I'd prefer just keying
> off the "-e" when the two colons are used. Cur
;) are
unaffected by the addition of the ':::' transfer mode.
Context diffs (against 2.4.6) for the code and documentation changes
are provided below, after some notes and gory details.
Share and enjoy --
JD Paul
