|
Author: Massimo Lusetti
Date: 06-08-01 18:57
You should separate the PATH from HOSTNAME with only one ':' to use SSH otherwise rsync still using it method to transport from server to clients.
Another error is that using the option --password-file is not useful when using ssh transport.
Quoting from man:
"This option allows you to provide a password in a file for accessing a remote rsync server. Note that`this option is only useful when accessing a rsync server using the built in transport, not when using a remote shell as the transport."
Regards,
Massimo
|
|
Reply To This Message
|
|
Author: Dan Langille
Date: 07-08-01 00:16
Massimo Lusetti wrote:
>
> You should separate the PATH from HOSTNAME with only one ':'
> to use SSH otherwise rsync still using it method to transport
> from server to clients.
Right you are. Thank you. I'll correct the article.
> Another error is that using the option --password-file is not
> useful when using ssh transport.
> Quoting from man:
> "This option allows you to provide a password in a file for
> accessing a remote rsync server. Note that`this option is
> only useful when accessing a rsync server using the built in
> transport, not when using a remote shell as the transport."
DOH! Thank you. I've updated the article. How's it look now?
|
|
Reply To This Message
|
|
Author:
Date: 08-04-02 21:03
Combining RSA authentication built in SSH with rsync, provides a very secure way to keep file trees in sync.
Perhaps your article can point this out, and possibly reference an article I believe you had about using SSH in this precise way.
Regards.
-lem
|
|
Reply To This Message
|
|
