ssh is run via rsync. My guess is this is just a
problem with running the older rsync.
Is that the case, and is there a workaround other than upgrading
rsync?
Here's some examples of how it's not reading my .ssh/config:
mysqldump is the single-use key. You can see that rsync --rsh=ssh
isn't
rsync.. Your sentence is a bit confusing :-)
Is that the case, and is there a workaround other than upgrading
rsync?
What works a lot better is understanding the rsync syntax.
Here's some examples of how it's not reading my .ssh/config:
...
$ rsync -a --rsh=ssh -F $HOME/.ssh/config -i $HOME/.ssh
On Thu, Nov 11, 2004 at 11:01:30PM +0100, Paul Slootman wrote:
When you use a double colon host::, then you're telling ssh to connect
directly to the rsync daemon running on that host using port 873. In
other words, ssh does not come into the equation, so it's pretty logical
that the .ssh
On Thu, Nov 11, 2004 at 04:47:32PM -0800, Wayne Davison wrote:
$ rsync -a --rsh=ssh -F $HOME/.ssh/config -i $HOME/.ssh/mysqldump
remotehost::
unknown host: remotehost
It looks like this command didn't even connect to the remote host, so
that would explain why the access times on the
On Thu, Nov 11, 2004 at 08:26:23PM -0800, Bill Moseley wrote:
So why isn't is using ssh?
Because you're using an archaic version of rsync that doesn't support
the feature you're trying to use. Upgrade to 2.6.3.
..wayne..
--
To unsubscribe or change options:
On Thu, Nov 11, 2004 at 09:06:49PM -0800, Wayne Davison wrote:
On Thu, Nov 11, 2004 at 08:26:23PM -0800, Bill Moseley wrote:
So why isn't is using ssh?
Because you're using an archaic version of rsync that doesn't support
the feature you're trying to use. Upgrade to 2.6.3.
Well, that's
