Usually the problem is that 'rmt', or similar, on a remote machine is
not where your side expects it is and providing a symbolic link, or two,
to "even-out playing field" resolves it.
Another possibility is to "pipe into rsh". I did not try that with
dump, which has an assorted list of compatibility problems, but
something like that worked for me just dandy:
tar <options> -cf - <what> | rsh <remote> -l backup cat "> <tape_device>"
Advantages are that you do not need a root access to <remote> but you
may use a "backup" account (as long as it has priviledges good enough to
write on a tape) and you do not need any manipulations with locations
of executables on a remote. If you have doubts about 'cat' writing on
a tape you may use 'dd' for that. Likely it cat be tuned better.
As long as you backup program (be it dump, tar, or something else) can
write on stdout you may use it in a pipe above instead of tar with
an equal success.
-- To unsubscribe: send e-mail to firstname.lastname@example.org with 'unsubscribe' as the subject. Do not send it to email@example.com
Copyright © 1995-1997 Red Hat Software. Legal notices