On Fri 04 Jan 2008, Gav wrote:
>
> $ rsync -rtlzv 123.456.789.000::websites /var/local/websites
>
> after about 2 minutes I get :-
>
> rsync: failed to connect to 123.456.789.000: Connection timed out (110)
> rsync error: error in socket IO (code 10) at clientserver.c(104)
> [receiver=2.6.9]
Hi All, finally got round to trying this again
> -Original Message-
> From: Matt McCutchen [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 2 January 2008 12:46 AM
> To: Gav
> Cc: rsync@lists.samba.org
> Subject: Re: error code 10 when using ::
>
> On Tue, 2
AIL PROTECTED]
> Sent: Wednesday, 2 January 2008 12:46 AM
> To: Gav
> Cc: rsync@lists.samba.org
> Subject: Re: error code 10 when using ::
>
> On Tue, 2008-01-01 at 17:44 +0900, Gav wrote:
> > This works :
> >
> > sudo rsync -rtlzv --delete [EMAIL PROTECTED]:/
On Wed, 2008-01-02 at 03:20 +0100, Olivier Thauvin wrote:
> IIRC, rsync protocol do not transfert password in clear text, but use a
> challenge method to perform the password verification.
>
> This mean either with rsync or ssh, the authentication is "secure". But
> saying
> both are secure is
Le mardi 01 janvier 2008, Matt McCutchen a écrit :
> > 2. Even the one that works requires me to enter my local root password
> > and then the remote root password. Is this secure enough?
>
> You'll have to decide that for yourself. SSH does encrypt the remote
> root password before sending it ove
On Tue, 2008-01-01 at 17:44 +0900, Gav wrote:
> This works :
>
> sudo rsync -rtlzv --delete [EMAIL PROTECTED]:/var/virtual/web
> /usr/local/websites
>
> This does not :
>
> sudo rsync -rtlzv --delete [EMAIL PROTECTED]::websites
> /usr/local/websites
>
> I created a [websites] section in a n
Hi All,
This works :
sudo rsync -rtlzv --delete [EMAIL PROTECTED]:/var/virtual/web
/usr/local/websites
This does not :
sudo rsync -rtlzv --delete [EMAIL PROTECTED]::websites
/usr/local/websites
I created a [websites] section in a new /etc/rsyncd.conf file then restarted
xinetd.
3 questions if