1rancid-cvs(1)               General Commands Manual              rancid-cvs(1)
2
3
4

NAME

6       rancid-cvs  -  initialize CVS, Subversion or git and rancid group files
7       and directories
8

SYNOPSIS

10       rancid-cvs [-V] [-f config_file] [group [group ...]]
11

DESCRIPTION

13       rancid-cvs creates the directories and  router.db(5)  for  each  rancid
14       group  and handles the revision control system (CVS, Subversion or git)
15       set-up in the location defined by the CVSROOT  in  rancid.conf(5).   It
16       must  be run after the initial installation and whenever a rancid group
17       is added.  If CVSROOT is a URL,  rancid-cvs  will  not  initialize  the
18       repository, the user must do this themselves.
19
20       rancid-cvs reads rancid.conf(5) to configure itself, then proceeds with
21       the initialization.  First of the CVS, Subversion or git repository, if
22       necessary,  and  then  for  each  of  the  rancid  groups listed on the
23       command-line   or   those   in   the   variable   LIST_OF_GROUPS   from
24       rancid.conf(5), if the argument is omitted.
25
26       Running  rancid-cvs  for  groups  which  already  exist  will not cause
27       problems.  If the group's directory already exists, the import into the
28       revision  control  system  will  be  skipped,  and if it's router.db(5)
29       already exists, it will not be altered.
30
31       The command-line options are as follows:
32
33       -V     Prints package name and version strings.
34
35       -f group_config_file
36              Specify an alternative rancid.conf.  The global rancid.conf file
37              is read by rancid-run.
38
39       The  best  method  for  adding  groups  is  by adding the group name to
40       LIST_OF_GROUPS in rancid.conf(5), then run rancid-cvs.  Do  not  create
41       the directories manually, allow rancid-cvs to do it.
42

SEE ALSO

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

CAVEATS

47       In  the  case  of  git,  the  groups  are not exactly imported into the
48       repository, rather a new repository is created for it, due to  the  way
49       that git handles, what it calls, sparse checkouts.  Instead, each group
50       is a separate repository under the CVSROOT directory.
51
52
53
54                               18 December 2014                  rancid-cvs(1)
Impressum