1
Template: cvsd/rootjail
4
_Description: Location of chroot jail:
5
cvsd can run in a chroot jail. This is the preferred method of
6
operation. Specify the location of the chroot jail. If you make this
7
'none' no chroot jail will be created and used.
8
A chroot file hierarchy will be created in the specified location.
10
Template: cvsd/maxconnections
13
_Description: The maximum number of connections that can be handled:
14
It is possible to specify a maximum number of connections that cvsd
15
can handle simultaneously. Specifying 0 (zero) will put no limit to
16
the number of connections.
21
_Description: Nice value cvsd should run at:
22
cvsd can be run at reduced priority so it will not take up too
23
many resources, especially if a user specifies a -z option to cvs.
24
The priority can also be increased (negative value here).
29
_Description: Umask cvsd should run at:
30
Specify the umask cvsd and cvs should use when creating files.
32
The umask should be specified as an octal value and represents
33
the permissions that should be taken away when creating a file
34
(e.g. using 027 will create files with mode 640 or rw-r-----).
39
_Description: Address and port on which cvsd will listen:
40
With the first argument you can specify the address cvsd should listen on.
41
The '*' address specifies that cvsd should listen on all addresses.
42
You can specify a IPv4 address, IPv6 address, a hostname or '*'.
44
The second argument is the service name (e.g. cvspserver) or port number
45
(default 2401) cvsd will listen on.
47
The address and port should be separated by a space and you can specify multiple
48
address-port combinations by separating them with spaces.
50
Template: cvsd/repositories
52
Default: /demo:/myrepos
53
_Description: Repositories to serve:
54
The whole idea of cvsd is to serve repositories. Specify a colon ':'
55
separated list of repositories to serve. The location of these repositories
56
is relative to the specified chroot jail (${rootjail}) and should start with a '/'.
58
The repositories here should be initialized by hand with something like
59
'cvs -d ${rootjail}/myrepos init' after which passwords can be set with
60
'cvsd-passwd ${rootjail}/myrepos anonymous'. See the file
61
/usr/share/doc/cvsd/README for details on creating repositories.
65
__Choices: coredumpsize, cputime, datasize, filesize, memorylocked, openfiles, maxproc, memoryuse, stacksize, virtmem
66
_Description: Select resources of pserver processes to limit:
67
The pserver wrapper can be configured to limit the resource usage that
68
a pserver process can have. These resource limits will be set on each
69
pserver process and not on the wrapper.
71
Choose from the list the resources that you want to limit.
72
You will be asked to specify limits about every resource you selected here.
74
Note that not all resources may be available on all systems and that
75
resources may be system and kernel specific so use these with caution.
76
The results of exceeding the set limits may also be system specific
77
but will most likely stop the cvs process and close the connection
78
(may be problematic with write access to cvs repository).
80
Template: cvsd/limit_coredumpsize
83
_Description: Maximum file size of a core dump:
84
Set this to 0 (zero) (should be the system default) to prevent core dumps.
85
Otherwise this limits the size of core dumps to the specified value.
87
This value may be specified with a suffix of 'b' (bytes), 'k'
88
(1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default.
90
Template: cvsd/limit_cputime
93
_Description: Maximum amount of cpu time consumed:
94
This limits the amount of cpu seconds the cvs process can use.
95
This will prevent too much cpu time from being allocated to a single connection.
97
This value can be formatted as 'mm:ss' or have a 'm' or 's'
98
suffix where 's' is default.
100
Template: cvsd/limit_datasize
103
_Description: Maximum size of program's data segment:
104
This limits the amount of memory the cvs program can use. This
105
specific item limits the size of the data segment.
107
This value may be specified with a suffix of 'b' (bytes), 'k'
108
(1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default.
110
Template: cvsd/limit_filesize
113
_Description: Maximum size of files created:
114
This limits the maximum size of a file created by cvs.
115
Note that the cvs pserver process needs to be able to create
116
lock files and possibly write history or other files so
117
don't set this to 0 (zero).
119
This value may be specified with a suffix of 'b' (bytes), 'k'
120
(1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default.
122
Template: cvsd/limit_memorylocked
125
_Description: Maximum amount of locked memory:
126
This limits the amount of memory the cvs process may lock.
127
cvs probably doesn't need to lock any memory at all.
129
This value may be specified with a suffix of 'b' (bytes), 'k'
130
(1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default.
132
Template: cvsd/limit_openfiles
135
_Description: Maximum number of open files:
136
This limits the amount of files and connections that the cvs
137
process can have open at a single moment. The cvs process needs
138
to access quite a few files so don't set this too low.
140
Template: cvsd/limit_maxproc
143
_Description: Maximum number of processes:
144
This limits the maximum number of processes that a single user may have.
145
cvs may need to spawn additional processes to run scripts or do subtasks
146
so don't set this too low.
148
Template: cvsd/limit_memoryuse
151
_Description: Maximum size of resident memory:
152
This specifies the amount of physical memory a process may have.
154
This value may be specified with a suffix of 'b' (bytes), 'k'
155
(1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default.
157
Template: cvsd/limit_stacksize
160
_Description: Maximum stack size:
161
This limits the size of the stack.
163
This value may be specified with a suffix of 'b' (bytes), 'k'
164
(1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default.
166
Template: cvsd/limit_virtmem
169
_Description: Maximum amount of virtual memory allocated:
170
This limits the total amount of virtual memory a process may have allocated.
172
This value may be specified with a suffix of 'b' (bytes), 'k'
173
(1024 bytes) or 'm' (1024*1024 bytes), where 'k' is the default.
175
Template: cvsd/limit_pthreads
178
_Description: Maximum number of threads:
179
This limits the number of threads that a single process may have.
181
This is not available under Linux so it is not in the list
182
for cvsd/limits. If Hurd has it it may be useful.
184
Template: cvsd/remove_chroot
187
_Description: Remove chroot jail containing repositories?
188
The following directory is configured as a chroot jail for cvsd:
190
You may choose to remove the chroot jail but you will also lose all the
191
repositories inside the chroot jail. If you have not backed up your
192
repositories you want to keep do not remove it now and manually remove
193
it later once your repositories are safe.
195
If you do choose to remove the chroot directory, all directories under
196
it will be removed, even if they are on another file system.
198
If you choose to keep the chroot jail please note that the cvsd user and
199
group will be removed so uid and gid file information may no longer be
added
removed
debian/templates
