1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
10 .de Sp \" Vertical space (when we can't use .PP)
16 .ie \\n(.$>=3 .ne \\$3
20 .TH "AMGETCONF" 8 "" "" ""
22 amgetconf - look up amanda.conf variables
25 \fBamgetconf\fR [\fIconfig\fR] \fIparameter\fR
29 looks up parameters in
30 \fBamanda.conf\fR, the
32 configuration file, or from the build and runtime environment, and returns their corresponding value.
38 assumes it is being run from the configuration directory and that
45 \fBbuild.\fR, the (case insensitive) string following the period is a build environment variable. Variables without a value (e.g.
47 on a system that does not support that type of file system) will not report an error and will return an empty string as the value. Flag variables (e.g.
48 \fBUSE_AMANDAHOSTS\fR) will return
50 if the flag is set or an empty string if it is not.
55 \fBdbopen.\fR, the string following the period is a program name and an
57 debug file will be created for the caller. The name of the file is returned.
62 \fBdbclose.\fR, the string following the period is a program name previously used with
63 \fBdbopen.\fR, followed by a colon (:) and the previously opened file name.
67 man page for more details about
71 Find out the path to the log file directory:
75 % amgetconf daily logdir
76 /usr/local/etc/amanda//daily
81 Find out the current tape type:
85 % amgetconf daily tapetype
91 Find out the default configuration directory:
95 % amgetconf daily build.CONFIG_DIR
96 /usr/local/etc/amanda/
101 Create, use and close a debug file in a script:
105 % set debug_file = `amgetconf daily dbopen.myscript`
106 % echo debug information >> $debug_file
107 % amgetconf daily dbclose.myscript:$debug_file
113 amgetconf: no such parameter \fBparam\fR
116 is not a known keyword (e.g. not a valid
118 keyword). In this case,
120 will write "\fBBUGGY\fR" to stdout as the value.