> I found that all the files required by amanda are "all over the place".
> Wouldnt it be a good idea to make amanda default to place everything in
> /home/amanda or at least $HOME? This way you would have ALL files at
> one position only .....
Blame the person that compiled the package!
./configure --prefix=/usr/local/amanda ...
But many sites, like myself, have different requirements. For instance
I like to have the program files separated from the config files, because
they reside on different disks (nfs-read-only vs writeable), and again
different for the local state variable files for each machine, etc.
You just have to specify some more options to configure to reach that goal.
The fundamental problem however is that amanda still has many pathnames
hardcoded into the binaries (by "./configure" above) that cannot be changed
in a precompiled system. When using precompiled binaries, you'll have to
live with the decisions of someone else for using Amanda.
But recompiling amanda is easier than changing the source...
--
Paul Bijnens, Lant Tel +32 16 40.51.40
Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61
http://www.lant.com/ email: [EMAIL PROTECTED]
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
