Re: [Dump-users] RE: Dump HOWTO

[Stelian P. <st...@ca...>]

On Tue, 27 Jun 2000 li...@li... wrote:

> and experienced several inconveniences/problems:
> 
> -- If I don't set up a .rhosts (so that ssh prompts for a passwd)
> then somehow it seems that dump has grabbed stdin, and won't pass
> on the password to ssh.  So the only way to dump remoely is to
> set up a .rhosts file (yuck).

Well, this was fixed some times ago if I recall well... 
What version of dump are you using?
> 
> -- suppose that above problem was solved.  There is then the
> inconvenience that said passwd would have to be entered for
> each invocation of dump (as well as for the mt), which makes
> running from a shell script hard/impossible. Ideally, I'd be 
> able to just log in one session, and run the shell script in that
> and have it all exit when done.

Take a look at ssh-agent. I think that's what you want...
> 
> Other than that, it seems to work fine (although ssh on a 486 on
> an old ne2000 ethernet is slowwww at 70kb a sec).

rsh is much faster, but not secure... You have to choose between
security and performance...

> Which brings me to another question:
> How much buffering, if any, does dump do, and is this adjustable?

Dump does no buffering (the buffering is done by the pipes used to
invoke rsh/ssh etc). But dump writes the data in chunks, and by
extending the size of the chunks you may have better performance
(see the -b option of dump).

Stelian.
-- 
Stelian Pop <sp...@ca...>| Too many things happened today
Captimark                      | Too many words I don't wanna say
Paris, France                  | I wanna be cool but the heat's coming up
                               | I'm ready to kill 'cause enough is enough
PGP key available on request   |              (Accept - "Up To The Limit")