On Sat, Jun 01, 2002 at 06:09:07PM -0500, Frank Smith wrote: > Amanda uses the full path to all the backup/restore programs that it was > configured with (and are fixed at compile time). So if Amanda was built > with your dump program as /usr/sbin/dump. but now it is /sbin/dump or > /usr/local/bin/dump, then you will get the 'program not available' error > even though 'dump' is somewhere in the Amanda user's path. (Disclaimer: > I'm a 'tar' user, and am assuming Amanda deals with ufsdump, vxdump, and > other variants of dump in a similar way to the way it finds GNU tar.) > Somewhere near the beginning of /tmp/amanda/amandad.*.debug you can > find the full command path that Amanda is trying to run. You can then > either make a link from there to the real program, or (probably better > for the long term) rebuild Amanda with the correct path. > > Good luck, > Frank > > --On Saturday, June 01, 2002 14:08:30 -0400 Kaan Saldiraner <[EMAIL PROTECTED]> >wrote: > > > Hello, > > > > Thanks for the responce .. I ran this command while su - to amanda > > > > export PATH=$PATH:/usr/sbin/:/usr/local/bin:/sbin:/bin > > > > Now amanda user can infact run the dump and restore without doing /sbin/dump > > ..etc. > >
Look in your config header file, <path_to_amanda_src>/config/config.h, for the path compiled in for the "#define's" of DUMP and GNUTAR. These absolute paths are what amcheck and friends are using. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
