>... I looked at amgetconf to
>find the configuration directory but could not find the right entry in
>amanda.conf.
This will do it:
amadmin xx version \
| grep CONFIG_DIR= \
| sed -e 's/.*CONFIG_DIR="//' -e 's/".*//'
I took a note to see if amgetconf could be taught to return some of the
more common hard coded compile time values.
>What about adding the output of this skript to the daily mail? At the
>moment I have to add it to the cron job and might miss "amflush"'es.
What about always running Amanda (amdump and amflush) from a wrapper
script? :-) That script can then do all sorts of localisms.
>Please feel free to modify the script. May it save you from worn out
>tapes at restore time.
A couple of thoughts. Once you know the config directory from above,
you might just cd there to avoid the duplicated names throughout the
script, and it also does some minimal permissions checking. This is
the technique most of the Amanda scripts already use.
cd $config_dir/$1 || exit 1
Using the following:
sort +0rn -1 +1
as the last sort shows the entries in decreasing reference count but
increasing label name, which might be a bit more readable.
>Johannes Niess
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
