control_rancid(1)
β¨ control_rancid β the manual, but make it cute β¨
okay bestie, gather round π this is control_rancid(1), a General Commands Manual page, and it's literally the little script that runs rancid for all the devices in one group. let's get into it π«Ά
π NAME
control_rancid β run rancid for devices of a group
πΈ SYNOPSIS
control_rancid [-V]
[-c commit_msg] [-f config_file] [-m mail_rcpt] [-r device_name] group
π¦ DESCRIPTION
control_rancid is a sh(1) script, no cap. its whole job is to parse a group's router.db(5), run rancid for each and every one of the devices, and possibly re-run rancid for the devices that failed collection (we don't abandon our fallen soldiers π), e-mail the diffs, and e-mail the error reports. full service, honestly.
it also creates and/or re-creates the .cvsignore / .gitignore files for each group. and for the configs sub-directory specifically, it includes ".old" β which is where a user may keep files they'd like to be ignored π.
β the command-line options are as follows:
-Vβ prints the package name and version strings. short, sweet, iconic.-c commit_msgβ specify an alternative SCM commit message. you get to write the little commit note yourself π-f group_config_fileβ specify an alternativerancid.conf. here's the tea: the globalrancid.conffile is read byrancid-run, which callscontrol_rancidfor each group, and thencontrol_rancidreads the group-specificrancid.confβ thereby overriding the global file. the group-specificrancid.confmay not exist, and that's fine, it's fine, everything's fine π
Default: <BASEDIR>/<group>/rancid.conf
-m mail_rcptβ specify the recipient of the diff mail, which is normallyrancid-<group>. the argument may be a single address, multiple comma separated addresses, or you can just say-mmultiple times, we're flexible like that β¨-r device_nameβ specify the name, exactly as it appears in therouter.db, of a particular device to collect and generate diffs for. the device must be marked"up"β οΈ no sneaking in a down device, bestie.
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. main character device energy π
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. like, it just hits different when you let rancid-run drive πβ¨
π SEE ALSO
and that's the whole page, bestie β no notes, you ate this π this version was served fresh from the General Commands Manual (source/version vibes), dated 22 December 2016. go forth and collect those configs πβ¨π¦
π¦ where this page comes from
- alpine 3.24: rancid-doc 3.14-r0 Β· BSD-3-Clause-No-Nuclear-License-2014
- debian bookworm: rancid 3.13-2+b1 Β· BSD-4-Clause
- debian trixie: rancid 3.14-1 Β· BSD-3-Clause
- epel 9: rancid 3.13-7.el9 Β· BSD with advertising
- fedora 43: rancid 3.13-16.fc43 Β· BSD-3-Clause
- fedora 43: rancid 3.14-1.fc43 Β· BSD-3-Clause
- fedora 44: rancid 3.13-17.fc44 Β· BSD-3-Clause
- fedora 44: rancid 3.14-1.fc44 Β· BSD-3-Clause
- nixos 26.05: rancid 3.13
- nixpkgs unstable: rancid 3.13
- ubuntu jammy: rancid 3.13-1 Β· BSD-4-Clause
- ubuntu noble: rancid 3.13-3 Β· BSD-4-Clause
- ubuntu questing: rancid 3.14-1
- ubuntu resolute: rancid 3.14-1build1 Β· BSD-3-Clause
- ubuntu stonking: rancid 3.14-1build1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms