Re: [Bug-tar] feature request: make --rsh more flexible.

[Doug McLaren]

On Thu, Aug 25, 2005 at 07:55:47PM -0600, Nathan wrote:

| I convince rsync to meet all these goals by passing the option
| "--rsh='ssh -i ~snapshot/.ssh/snapshot_key_without_password.secret -u
| snapshot'".  When rsync runs I assume it appends whatever the remote
| command is to this option value.
| 
| However, if I try this with gnu tar (v 1.14) it complains that no such
| executable is found.
| 
| The gnu tar handling seems simpler and somehow "safer" to me, but less 
flexible.
| 
| Is there a way to handle this configuration without resorting to
| demanding the reading versus writing process have the same user name
| on both hosts?  (Short of changing the --rsh semantics to act like
| rsync...)

Create a shell script --

   #!/bin/sh
   exec ssh -i ~snapshot/.ssh/snapshot_key_without_password.secret -u snapshot 
"$@"

and make it executable and invoke it from tar instead of ssh.

Depending on which /bin/sh you have, ~snapshot may not work -- you may
need to put the actual path in there.

But I do agree, the way it works in rsync is more convenient.  For
example, I often use --rsh="ssh -c blowfish" to speed things up.

Actually, I now use rsync instead of tar for many things that I used
to use tar for, but rsync has it's own set of quirks as well.  At
least with tar I'm almost always sure of what I'll get on the remote
end :)

-- 
Doug McLaren, address@hidden, AD5RH
`What's the use of happiness? It can't buy you money.' -Henny Youngman