tarsnap.conf man page

tarsnap.conf — configuration file for tarsnap(1)

Description

The tarsnap.conf file is read by the tarsnap(1) utility and specifies default options which will be ignored if the options in question are specified at the command line. Options may be specified in /etc/tarsnap.conf and/or ~/.tarsnaprc; if the two files conflict, the user's local configuration takes precedence.

The tarsnap.conf file(s) contain lines consisting of a case-sensitive option name and zero or one parameters depending upon the option. Empty lines and lines starting with a Ql # character are ignored.

If a parameter begins with a Ql ~ character, it will be replaced by the value of the HOME variable (the current user's home directory).

The following options may be specified:

aggressive-networking

cachedir cache-dir

checkpoint-bytes bytespercheckpoint

disk-pause X

exclude pattern

humanize-numbers

include pattern

insane-filesystems

keyfile key-file

lowmem

maxbw

maxbw-rate

maxbw-rate-down

maxbw-rate-up

nodump

normalmem

no-aggressive-networking

no-config-exclude

no-config-include

no-disk-pause

no-humanize-numbers

no-insane-filesystems

no-maxbw

no-maxbw-rate-down

no-maxbw-rate-up

no-nodump

no-print-stats

no-quiet

no-snaptime

no-store-atime

no-totals

print-stats

quiet

snaptime file

store-atime

totals

verylowmem

Each option is handled the same way as the corresponding --option; see tarsnap(1) for more details. Note that the normalmem and no-* options are only useful in the user-specific ~/.tarsnaprc configuration file, at which point they act to override options set in the global /etc/tarsnap.conf configuration file.

Files

/etc/tarsnap.conf
The system global tarsnap.conf configuration file. Parameters specified here only take effect if they are not specified via the current user's local configuration file or via the command line.
~/.tarsnaprc
The tarsnap.conf configuration file for the current user. Parameters specified here take effect unless they are specified via the command line.

See Also

tarsnap(1)

Referenced By

tarsnap(1).

July 10, 2009