ibod_cf(4) [debian man page]
IBOD.CF(4) Kernel Interfaces Manual IBOD.CF(4) NAME
ibod.cf - configuration file for ibod (ISDN Bandwidth On Demand) DESCRIPTION
This file contains the initial configuration values for the ibod daemon. Each line contains a keyword and a value. Boolean attributes are set with 0 or 1 which corresponds to false and true respectively. A boolean attribute not specified at all is always false. Lines beginning with # are treated as comments and will be ignored. IMPORTANT RULES! 1. Keywords are case sensitive. 2. Kewords must begin at the first column. 3. Keywords and values must be separated by exactly one (1) space or tab character. This file is re-read every time ibod receives SIGHUP (1) signal. OPTIONS DEVICE <name> Name of ISDN PPP device. Default is ippp0. ENABLE 1|0 Enable/disable bandwidth-on-demand. Default is enable (1). INTERVAL <n> Specify the sample time interval in ms. Default is 500 ms. FILTER <n> Defines "filtering factor". A value of 10 means that the average bytes/sec value measured over 10 intervals must pass the limit defined by LIMIT to bring up or down the slave link. Default is 5. LIMIT <n%> Specifies percentage loading of the channel at which it is necessary to up or down channels. This sets both up and down limits to the same value. Note that this has changed from version 1.4. UPLIMIT <n%> Specifies percentage loading of the channel at which it is necessary to up channels. Default is 90. DOWNLIMIT <n%> Specifies percentage loading of the channel at which it is necessary to down channels. Default is 80. STAYUP 0|1 Enable/disable slave channel stay up function. If enabled, the second channel (slave link) will stay up even if the average bytes/sec decrease the value defined by LIMIT. In this case the slave link will stay up until hangup time is reached. (Example: isdnctrl huptimeout ippp1 60) If disabled the slave link will be brought down in the same way it was brought up. Default is 0. STAYUP_TIME <n> Defines the minimum time in seconds the second channel will unconditionally stay up after it has been brought up. Default value is 30. STAYDOWN_TIME <n> Defines the minimum time in seconds the second channel will unconditionally stay down after it has been brought up. Default value is 10. FULL <n> Defines the maximum throughput in bytes/sec one channel can transmit. Default value is 7500. MAX_CHANNELS <n> Defines the maximum number of channels the connection can run with. Default is 2. SEE ALSO
ibod(1) and xibod(1) AUTHOR
Jan Obladen, obladen@datenwelt.net Bjoern Smith, Smith@Compound.SE Paul Martin <pm@debian.org> IBOD.CF(4)
Check Out this Related Man Page
SNAPPER-CONFIGS(5) Filesystem Snapshot Management SNAPPER-CONFIGS(5) NAME
snapper-configs - Configuration files for snapper configs DESCRIPTION
Each file /etc/snapper/configs/* describes a snapper config. VARIABLES
The following is a list of variables that can be present in the configuration file. Boolean values must be "yes" or "no". SUBVOLUME=path Path of the subvolume or mount point. There is no default value. The value must always be specified. FSTYPE=value Filesystem type for the subvolume. Default value is "btrfs" but it's recommended to always specify the filesystem type. ALLOW_USERS=users List of users allowed to operate with the config. The user-names must be separated by spaces. Spaces in usernames can be escaped with a "". Default value is "" but "root" is always implicitly included. ALLOW_GROUPS=groups List of groups allowed to operate with the config. The group-names must be separated by spaces. Spaces in group-names can be escaped with a "". Default value is "". BACKGROUND_COMPARISON=boolean Defines whether pre and post snapshots should be compared in the background after creation. Default value is "no". NUMBER_CLEANUP=boolean Defines whether the number cleanup algorithm should be run for the config. Default value is "no". NUMBER_MIN_AGE=seconds Minimal age for snapshots to be deleted by the number cleanup algorithm. Default value is "1800". NUMBER_LIMIT=number Defines how many snapshots the number cleanup algorithm should keep. The youngest snapshots will be kept. Default value is "50". TIMELINE_CREATE=boolean Defines whether hourly snapshots should be created. Together with the timeline cleanup algorithm this will create a collection of snapshots with more snapshots is the near past and less snapshots in the far past. Default value is "no". TIMELINE_CLEANUP=boolean Defines whether the timeline cleanup algorithm should be run for the config. Default value is "no". TIMELINE_MIN_AGE=seconds Minimal age for snapshots to be deleted by the timeline cleanup algorithm. Default value is "1800". TIMELINE_LIMIT_HOURLY=number Defines how many hourly snapshots the timeline cleanup algorithm should keep. An hourly snapshots is the first snapshot in an hour. The youngest hourly snapshots will be kept. Default value is "10". TIMELINE_LIMIT_DAILY=number Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The youngest daily snapshots will be kept. Default value is "10". TIMELINE_LIMIT_MONTHLY=number Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The youngest daily snapshots will be kept. Default value is "10". TIMELINE_LIMIT_YEARLY=number Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The youngest daily snapshots will be kept. Default value is "10". EMPTY_PRE_POST_CLEANUP=boolean Defines whether the empty-pre-post cleanup algorithm should be run for the config. Default value is "no". EMPTY_PRE_POST_MIN_AGE=seconds Minimal age for snapshots to be deleted by the empty-pre-post cleanup algorithm. Default value is "1800". HOMEPAGE
http://snapper.io/ AUTHORS
Arvin Schnell <aschnell@suse.de> SEE ALSO
snapper(8), snapperd(8) 0.1.7 2013-07-09 SNAPPER-CONFIGS(5)