Manual Reference Pages - RANCID-RUN (1)
rancid-run - run rancid for each of the groups
rancid-run [-V] [
[group [group ...]]
rancid-run is a
script to run
for a set of rancid group(s).
to configure itself, then uses
for each rancid group. The set of rancid groups can either be provided
as command-line arguments or via the
LIST_OF_GROUPS variable in
if the group argument is omitted.
A lock file is maintained per-group to prevent simultaneous runs for a given
The lock file will be named
.<group>.run.lock and will be located in
$TMPDIR (see below).
A log file is produced under
$LOGDIR/logs for each rancid group processed. The file name will be <group>.YYYYMMDD.HHMMSS
(year month day . hour minute second).
rancid-run is normally used to run rancid from
0 * * * * /usr/local/rancid/bin/rancid-run
The command-line options are as follows:
Prints package name and version strings.
-f rancid.conf |
Specify an alternate configuration file.
-m mail_rcpt |
Specify the recipient of diff mail, which is normally rancid-<group>. The
argument may be a single address, multiple comma separated addresses, or
-m may be specified multiple times.
-r device_name |
Run rancid for a single device,
device_name should be name, as it appears in a groups router.db. The device must be
marked "up". If a group is not specified on the command-line, rancid will
be run against any group in which the device_name appears.
-r option alters the subject line of the diff mail. It will begin
with <group name>/<device name> rather than just the group name alone.
rancid-run utilizes the following environment variables from
Location of group directories, etc. This is set to the "localstatedir"
by the configure script at installation time.
List of rancid groups to collect.
Search path for utilities.
Directory to hold temporary and lock files.
If rancid fails to run or collect a devices configuration, the particular
groups log file (mentioned above) should be consulted. Any errors produced
by the revision control system (CVS, Subversion, or git) or any of the rancid
scripts should be included there, whether they be a botched cvs tree, login
authentication failure, rancid configuration error, etc.
If the log file produces no clues, the next debugging step should be run the
commands manually. For example, can the user who runs rancid login to the
device with clogin hostname, and so on.
rancid-run configuration file.
DO NOT leave temporary files in the <group name>/configs directory, they WILL
be removed by
|--> ||RANCID-RUN (1) ||17 December 2014 |
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.