12 amgetconf \- look up amanda.conf variables
21 looks up parameters in
23 the Amanda configuration file,
24 or from the build and runtime environment,
25 and returns their corresponding value.
31 assumes it is being run from the configuration directory and that
39 the (case insensitive) string following the period
40 is a build environment variable.
41 Variables without a value (e.g.\&
43 on a system that does not support that type of file system)
44 will not report an error and will return an empty string as the value.
45 Flag variables (e.g.\&
49 if the flag is set or an empty string if it is not.
55 the string following the period is a program name and an Amanda debug
56 file will be created for the caller.
57 The name of the file is returned.
63 the string following the period is a program name previously used with
65 followed by a colon (:) and the previously opened file name.
69 man page for more details about Amanda.
71 Find out the path to the log file directory:
75 % amgetconf @DEFAULT_CONFIG@ logdir
76 @CONFIG_DIR@/@DEFAULT_CONFIG@
80 Find out the current tape type:
84 % amgetconf @DEFAULT_CONFIG@ tapetype
89 Find out the default configuration directory:
93 % amgetconf @DEFAULT_CONFIG@ build.CONFIG_DIR
98 Create, use and close a debug file in a script:
102 % set debug_file = `amgetconf @DEFAULT_CONFIG@ dbopen.myscript`
103 % echo debug information >> $debug_file
104 % amgetconf @DEFAULT_CONFIG@ dbclose.myscript:$debug_file
109 amgetconf: no such parameter "\fIparam\fR"
112 is not a known keyword
118 will write "\fBBUGGY\fR" to stdout as the value.