Just curious, what is the reason for not having modules when using SSH ?
Isn't SSH
just another transport between the rsync client and server ?
Also, should we use modules names in the actual sync commands or are they
simply
flatten to a single file list (very dangerous) ?
We are accessing the remote servers from a dynamic list so setting the SSH
forwarding
tunnels are not that simple (at least for me). Any idea how to handle it.
Thanks,
Tal
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Pierre Abbat
> Sent: Saturday, February 10, 2001 3:23 PM
> To: Tal Dayan; [EMAIL PROTECTED]
> Subject: Re: Help: how to get the module list
>
>
> On Sat, 10 Feb 2001, Tal Dayan wrote:
> >We have a backup script (on Linux x86 6.0) that retrieves the list of
> >modules (the '[name'] things defined in rsyncd.conf) of a remote
> server and
> >than sync it in. This is done using the command:
> >
> >rsync --rsh=/usr/bin/rsh --recursive --times myserver.com::
> >
> >This lists the modules, one per line in the form '<module_name>
> ><module_description>'
> >
> >Now we are trying to switch to a secure connection over ssh using the
> >command:
> >
> >rsync -e ssh --recursive --times myserver.com:
> >
> >this however gives a long list of the files on the remote server
> rather then
> >the list of modules. I find it strange since all we change is
> the transport.
> >
> >How can we get the list of modules over a secure connection ?
>
> Modules aren't used when you use rsync over ssh. You might try
> forwarding port
> 873 (the rsync port) over ssh from some unused local port and
> using the --port
> option to rsync to that port on localhost.
>
> phma
>
>
