control_rancid(1) [debian man page]

control_rancid(1)					      General Commands Manual						 control_rancid(1)

NAME

       control_rancid - run rancid for devices of a group

SYNOPSIS

       control_rancid [-V] [-m mail_rcpt] [-r device_name] group

DESCRIPTION

       control_rancid  is  a  sh(1) script to parse a group's router.db(5), run rancid for each of the devices, possibly re-run rancid for devices
       that failed collection, e-mail diffs, and e-mail error reports.

       The command-line options are as follows:

       -V     Prints package name and version strings.

       -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
	      Specify  the  name,  as  it  appears in the router.db, of a particular device to collect and generate diffs for.	The device must be
	      marked "up".

	      The -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.

       control_rancid  is  normally (and best) run via rancid-run(1) which provides a locking mechanism on a group basis and saves output in a log
       file for each group.

SEE ALSO

       rancid-run(1), rancid.conf(5), router.db(5)

								  5 October 2006						 control_rancid(1)

rancid-cvs(1)						      General Commands Manual						     rancid-cvs(1)

NAME

       rancid-cvs - initialize CVS or Subversion and rancid group files and directories

SYNOPSIS

       rancid-cvs [-V] [group [group ...]]

DESCRIPTION

       rancid-cvs  creates the directories and router.db(5) for each rancid group and handles the revision control system (CVS or Subversion) set-
       up.  It must be run after installation and whenever a rancid group is added.

       rancid-cvs reads rancid.conf(5) to configure itself, then proceeds with the initialization.  First of the CVS or Subversion repository,	if
       necessary,  and	then for each of the rancid groups listed on the command-line or those in the variable LIST_OF_GROUPS from rancid.conf(5),
       if the argument is omitted.

       Running rancid-cvs for groups which already exist will not cause problems.  If the group's directory already exists, the  import  into  the
       revision control system will be skipped, and if it's router.db(5) already exists, it will not be altered.

       The command-line options are as follows:

       -V     Prints package name and version strings.

       The  best  method  for  adding  groups  is  add	the group name to LIST_OF_GROUPS in rancid.conf(5), then run rancid-cvs. Do not create the
       directories manually, allow rancid-cvs to do it.

SEE ALSO

       cvs(1), rancid.conf(5), router.db(5), svn(1)

								  5 October 2006						     rancid-cvs(1)