1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124
|
Template: cvs/repositories
Type: string
Default: /srv/cvs
_Description: Repository directories:
Please list the directories that are the roots of your repositories,
separated by colons.
.
These repositories can be exported by the pserver, have their history
files rotated automatically every week, and general repository security
checks will be performed on them.
.
If you wish to create a new repository, enter the path where you wish to
create it. You will then be given the option of creating it later.
Template: cvs/badrepositories
Type: select
_Choices: create, ignore, reenter
Default: create
#flag:translate!:3
_Description: Method to fix invalid repositories:
The following items you entered are not directories or do not contain a
CVSROOT subdirectory:
.
${badreps}
.
If you have not yet created these repositories, they can be created by
selecting 'create'. You could also select 'ignore' and use the
'cvs-makerepos' command to create them, or create them individually using
'cvs init'.
.
You can also choose to 'reenter' your repositories list.
Template: cvs/rotatehistory
Type: select
_Choices: yes, no, individual
Default: no
_Description: Weekly rotation for history files in repositories:
Weekly rotation of history files is primarily useful for servers with a
lot of activity. The script /etc/cron.weekly/cvs will rotate the history
files. Select "individual" if you want to control rotation on a
per-repository basis.
Template: cvs/rotate_individual
Type: boolean
Default: true
_Description: Rotate the history files of the repository in ${repos} each week?
Template: cvs/rotatekeep_nondefault
Type: select
_Choices: yes, no, individual
Default: no
_Description: Change the number of kept history files:
When rotating history files in repositories, by default the previous 7 are
kept. Choosing "yes" will allow you to change this number globally.
Choosing "individual" will allow you to specify the number of days to
keep history files for individual repositories.
Template: cvs/rotatekeep
Type: string
Default: 7
_Description: Number of previous history files to keep (global setting):
Please choose how many previous history files should be kept when the
history files in your repositories are rotated each week.
Template: cvs/rotatekeep_individual
Type: string
Default: 7
_Description: Number of previous history files to keep in ${repos}:
Please choose how many previous history files should be kept in
${repos} when the history files in your repositories are rotated
each week.
Template: cvs/pserver
Type: boolean
Default: false
_Description: Should the CVS pserver be enabled?
The CVS pserver is a client-to-server mechanism which can be used by CVS as a
replacement for the standard "server" method, which uses "rsh", or an rsh
compatible program, such as ssh. It is more efficient than the standard
server protocol, also supporting its own password files, making it more
secure. However, it may be a security risk, and used to contain a security
problem whereby a remote connection may have been able to read the passwd
or other security-related files on the system. Read README.Debian for more
details, and extra ways to secure the pserver.
.
It is not recommended to choose this option. CVS now only allows
access to particular repositories specified on the command line. When
chosen, it will be installed in inetd, using tcpd wrappers.
Template: cvs/pserver_repos
Type: select
_Choices: all, some
Default: all
_Description: Repositories to export via the pserver:
Template: cvs/pserver_repos_individual
Type: boolean
Default: true
_Description: Do you want the repository ${repos} exported via pserver?
Template: cvs/pserver_setspawnlimit
Type: boolean
Default: false
_Description: Change the maximum pserver processes spawned in one minute?
When running a pserver, inetd's default limit of allowing 40 connections
in 1 minute can easily be exceeded if a script calls CVS individually on
many files over a pserver connection. This limit is designed to stop
system load from rising too high if the service is continually failing.
.
Thus, a more sensible default limit for most systems is 400. However, if
you are running an inetd clone which does not support the syntax
"nowait.[limit]", you will need to not set a limit using this method.
Template: cvs/pserver_spawnlimit
Type: string
Default: 400
_Description: Inetd spawn limit for the CVS pserver:
When running a pserver, inetd's default limit of allowing 40 connections
in 1 minute can easily be exceeded if a script calls CVS individually on
many files over a pserver connection. This limit is designed to stop
system load from rising too high if the service is continually failing.
.
Thus, a more sensible default limit for most systems is 400.
|