|
Re: question about new disks
2006-10-20 14:04:33
actually, i couldnt find amadmin anywhere on my client. I did just come
across the fact that /bin/tar is where GNUTAR is looking. I now see it
by using your command (on the amanda server), but i found it by doing
"strings /usr/lib/amanda/runtar".
I guess the easiest way for me to fix this problem is to make a symlink
from the /usr/local/bin/tar to /bin/tar (of course I'll backup the
existing tar first). With a little foresight, the best way to handle
this is to configure amanda for gnutar somewhere in the amanda dir and
create a symlink on each client machine?
Thanks again.
Steve
Jon LaBadie wrote:
On Fri, Oct 20, 2006 at 12:07:03PM -0400, Steven Settlemyre wrote:
someone hinted to me that since my client is a solaris machine, the
GNUTAR program specified in my dumptype might not be correct. I know on
my Linux machines, gnutar is /bin/tar, but my solaris machine is at
/usr/local/bin/tar. could this be the problem? also, how would I get my
dumptype to use this path?
Thanks
Jon LaBadie wrote:
On Fri, Oct 20, 2006 at 10:15:04AM -0400, Steven Settlemyre wrote:
Server:
Debian (sarge) Linux.
amanda version: 2.5.0p2
Client:
tar: (GNU tar) 1.13.19
amanda-client: ? how do i find this?
On any amanda installation,
amadmin - version
You thanked me but probably did not run my suggestion.
Lots of other things print out with the version cmd
including the path to gnutar that will be used.
It is hardcoded at compile time, not a runtime setting.
For that reason I always run configure with the option
to specify where gnutar lives and say it lives in
/usr/local/libexec/amgtar. Then I make amgtar be a
copy or a link of whichever tar I wish to use.
|
|
|
