Le Jeudi 22 Mars 2007 20:55, Wayne Davison a écrit :
> On Thu, Mar 22, 2007 at 06:22:11PM -0300, Roberto Pereyra wrote:
> > Seems like a ssh issue because if I use the standard rsync port
> > (without shh) works well.
>
> Those are two different things. Without ssh, you're connecting to an
> exis
On Thu, Mar 22, 2007 at 06:22:11PM -0300, Roberto Pereyra wrote:
> Seems like a ssh issue because if I use the standard rsync port
> (without shh) works well.
Those are two different things. Without ssh, you're connecting to an
existing rsync daemon. With ssh (via -e), you're using a remote she
Roberto Pereyra wrote:
> Hi
>
> I running a rsync server using version 2.6.3pre1 in a Solaris 10 server.
>
> When I try to use ssh to encrypt my data, the rsync client fails with
> this message:
According to documentation what you try simply isn't possible "directly".
If you want transport en
Hi Mark
Yes I can ssh login and if write a wrong user/password the system
promt for a new one, without error.
Seems like a ssh issue because if I use the standard rsync port
(without shh) works well.
Thanks
roberto
2007/3/22, Mark Schoonover <[EMAIL PROTECTED]>:
Roberto Pereyra wrote:
> H
Roberto Pereyra wrote:
> Hi
>
> I running a rsync server using version 2.6.3pre1 in a Solaris 10
> server.
>
> When I try to use ssh to encrypt my data, the rsync client fails with
> this message:
>
>
> rsync -avz -e ssh winbox.exe [EMAIL PROTECTED]::backups
> Password:
> rsync: connection
Hi
I running a rsync server using version 2.6.3pre1 in a Solaris 10 server.
When I try to use ssh to encrypt my data, the rsync client fails with
this message:
rsync -avz -e ssh winbox.exe [EMAIL PROTECTED]::backups
Password:
rsync: connection unexpectedly closed (0 bytes received so far) [s
