On Thu, 2 Jun 2005, Randy McMurchy wrote: > M.Canales.es wrote these words on 06/02/05 13:11 CST: > > > Depend on how is configured the server that you want to conect to. > > > > That is very similar to CVS or Subversion. You can to use the internal > > autenthication method or a more secure external one. > > That would make sense. However, the default BLFS build at this > point uses ssh as the default transport. Looking at the source > code, best I can figure is that unless you pass additional > parameters to the configure script, rsync will attempt to use > ssh as the transport. >
Correct, and use of rsh should be discouraged (and has been discouraged by the rsync developers for some time). Well spotted, Randy. > The internal mechanics aren't really the issue though. My question > is more about the policy that run-time dependencies aren't listed > unless there is a special exception. To me, this qualifies as a > special exception. > > I will defer to whatever Bruce thinks is best, as policy is to not > list non-compile time dependencies. What it boils down to is: > > 1. List SSH as a recommended dependency, or Sounds preferable to me (although people using rsync to maintain backups on the _same_ host or over an nfs share can probably get away without it). > 2. Place a note in the book about SSH (problem is, I'm not really > qualified to write this note, as I'm not familiar enough with the > internal mechanics of rsync). > > It needs to talk to remote hosts (any time the path to one or other file includes ':' or '::') to start a shell, sometimes this requires a password (there is more detail in one of the man pages about why it can't use scp). Ken -- das eine Mal als Trag�die, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
