modules madness / ssh regardless of daemon

tim.conway at tim.conway at
Tue Nov 20 07:27:34 EST 2001

You're fine.  You can either use the rsyncd (defiance::auth), thus going 
to your rsyncd, or you can use -e ssh, using ssh as the remote transport.
rsync -options -e ssh remotehost:/path/to/auth /path/to/auth/mirror.
if you use the second version, the rsyncd.conf is irrelevant.... you don't 
have to relate a path as a named module... you just use the path... 

Tim Conway
tim.conway at
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn, 
".\n" '
"There are some who call me.... Tim?"

Brian Clark <brianj at>
Sent by: rsync-admin at
11/19/2001 11:50 AM
Please respond to Brian Clark

        To:     rsync at
        cc:     (bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        Re: modules madness / ssh regardless of daemon

Hi Tim,

@ 1:40:43 PM on 11/19/2001, tim.conway at wrote:

tcpc> -e ssh is for external transport. So is the single colon syntax
tcpc> (defiance:auth) Use this cmdline: rsync -avz defiance::auth

OK, I should have mentioned this earlier, and I forgot. I don't have
rsh on [either] system because I've been told over and over that it's
insecure (or was that something else?). Anyway, I think that's before
my time, or maybe not. All I've ever know are telnet, then ssh, so
that's what I immediately stuck to when rsync.

I'm now wondering how I'm going to mirror anything unattended without
having a valid ssh login/password in a file some where. On top of
that, -e ssh renders rsyncd.conf useless (hosts access, auth users,
etc.). :-\

 -Brian Clark | PGP is spoken here: 0xE4D0C7C8
  Please, DO NOT carbon copy me on list replies.

-------------- next part --------------
HTML attachment scrubbed and removed

More information about the rsync mailing list