1 <?xml version="1.0" encoding="UTF-8"?>
4 <database xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
5 xsi:noNamespaceSchemaLocation="file:configuration.xsd">
7 <!-- Global configuration -->
8 <collection name=".default" use="optional">
9 <collection name="init" type="fixed">
11 <description>Default mtab file</description>
15 <link name="vdirbase">
16 <default>/vservers</default>
19 <collection name="apps">
20 <collection name="pkgmgmt">
22 <default>/vservers/.pkg</default>
24 <data name="apt.conf">
26 The default apt.conf which is going to be used. It is overridden by
27 distribution specific configuration file.
32 <collection name="debootstrap">
33 <scalar name="mirror">
35 The Debian mirror to use with the 'debootstrap' program
40 When the 'debootstrap' package is not installed; fetch it from this uri and
41 install it at a temporary place.
46 <collection name="vprocunhide">
49 A list of files which will be made visibly by vprocunhide. Wildcards are
50 allowed and anything ending in '/' will be processed recursively. When this file exists,
51 it overrides the defaults in SYSDEFAULTDIR/vprocunhide-files. The entries there must be
52 absolute filenames inclusive the leading '/proc'.
57 <collection name="init">
60 A symlink to the TTY device where input/output will be redirected from/to
61 at startup via initscript.
66 <collection name="vunify">
69 Static list of excluded files.
75 <collection name=".distributions" use="optional">
76 <collection name="dist" type="symbolic">
81 <data name="apt.conf">
83 The default apt.conf which is going to be used. It overrides the apt.conf
84 from CONFDIR/.defaults/apps/pkgmgmt.
87 <program name="initpre">
89 Script which will be executed before packages will be installed.
92 <parameter name="confdir">
94 The configuration directory of the vserver which is going to be set up.
97 <parameter name="vserver">
99 The pathname of the vserver binary.
104 <program name="initpost">
106 Script which will be executed after packages are installed.
109 <parameter name="confdir">
111 The configuration directory of the vserver which is going to be set up.
114 <parameter name="vserver">
116 The pathname of the vserver binary.
122 <collection name="pkgs">
124 Contains files with packages.
128 File which contains the name of packages. On top of file the special
129 keywords '--reinstall' and '--can-fail' are possible.
134 <collection name="pubkeys">
136 Directory with GPG pubkeys which are used to sign the packages of this
141 <collection name="apt">
143 Default content of the /etc/apt/ directory.
147 <collection name="rpm">
149 Default content of the /etc/rpm directory.
155 Directory which overrides /usr/lib/rpm.
158 <link name="execdir">
160 Directory with all executables and libraries which are required for this
168 <!-- Vserver configuration -->
169 <collection name="vserver-name" type="symbolic">
171 The configuration directory for the vserver vserver-name.
176 Path of the vserver root directory
182 Path of the vserver run directory
186 <link name="run.rev">
188 Path of the vserver run reverse directory
192 <list name="bcapabilities">
194 [experimental; name is subject of possible change] Contains the system capabilities. See
195 <ulink url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/bcaps-v13.c?rev=HEAD">lib/bcaps-v13.c</ulink>
199 <list name="ccapabilities">
201 [experimental; name is subject of possible change] Contains the context capabilities. See
202 <ulink url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/ccaps-v13.c?rev=HEAD">lib/ccaps-v13.c</ulink>
206 <hash name="schedule">
208 [experimental; name is subject of possible change] Contains the scheduler parameters,
211 The Hard CPU limit uses a mechanism called a Token Bucket.
212 the concept is simple: you have a bucket of a certain size
213 which is filled with a specified amount R of tokens each
214 interval T until the maximum is reached (excess tokens
215 are spilled). At each timer tick, a running process consumes
216 one token from the bucket, unless the bucket is empty. If the
217 bucket is empty the process is put in the hold queue. When the
218 bucket has been refilled to at least M tokens, all on hold
219 processes are rescheduled.
222 <key name="fill-rate">
224 Amount of tokens append to the bucket each interval.
227 <key name="interval">
229 The intervall between refills of amount 'fill_rate'. This value is express in ticks.
234 Initial bucket contents.
237 <key name="tokens-min">
239 The minimum amount of tokens required to unhold processes
242 <key name="tokens-max">
247 <key name="priority-bias">
256 Contains the name of the vserver. When not given, the basename of the directory
257 will be assumed as this name.
262 The nice-level on which the vserver will be started.
265 <list name="capabilities">
267 Contains per line a capability. This file is used for the 2.4
268 kernel only; for 2.6 use 'bcapabilities'.
271 <scalar name="shell">
273 Contains the pathname of the shell which will be used by the "vserver ... enter"
279 Contains per line a flag. See
280 <ulink url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/cflags-v13.c?rev=HEAD">lib/cflags-v13.c</ulink>
284 <element name="fakeinit">
286 The new process will believe it is process number 1. Useful to
287 run a real /sbin/init in a vserver. Warning: this flag should
288 not be used unless you know what you are doing. Often, it is
289 better to use the 'plain' initstyle.
292 <element name="lock">
294 The new process is trapped and can't use chcontext anymore.
297 <element name="sched">
299 The new process and its children will share a common
302 <element name="nproc">
304 Limit the number of process in the vserver according to
305 ulimit setting. Normally, ulimit is a per user thing.
306 With this flag, it becomes a per vserver thing.
309 <element name="private">
311 No one can join this security context once created.
314 <element name="ulimit">
316 Apply the current ulimit to the whole context
321 <scalar name="context">
323 Contains the context which shall be used for the vserver.
328 The fstab file for the vserver. Entries in this file will be mounted within the
329 network context of the vserver; this means that mount will be called as 'chbind <options>
330 mount ...'. Use the 'fstab.local' file when you do not want this behavior, but in most cases
331 the 'fstab' file should be used.
334 <data name="fstab.local">
336 The fstab file for the vserver. In opposite to the normal 'fstab' file, the
337 mounting happens in the local network context. Currently there is no way to mix entries of
338 both files; 'fstab' will be always processed before 'fstab.local'.
342 <collection name="apps">
343 <collection name="init">
346 The initial-mtab which will be used for the vserver.
350 <scalar name="style">
352 Contains the init-style.
355 <enumeration value="sysv"/>
356 <enumeration value="plain"/>
357 <enumeration value="minit"/>
358 <enumeration value="gento"/>
362 <scalar name="runlevel">
363 <description>The start runlevel.</description>
366 <scalar name="runlevel.start">
367 <description>The start runlevel.</description>
370 <scalar name="runlevel.stop">
371 <description>The stop runlevel.</description>
374 <scalar name="killseq">
376 Contains the 'signal [wait signal]*' sequence which is used to stop the
381 <list name="cmd.start">
383 The command which is used to start the vserver. Each option must be on a
388 <list name="cmd.start-sync">
390 The command which is used to wait on the vserver after it has been
391 started. Each option must be on a separate line. This file will be ignored when the
392 'sync' does not exist and the '--sync' option was not used.
396 <list name="cmd.stop">
398 The command which is used to stop the vserver. Each option must be on a
403 <list name="cmd.stop-sync">
405 The command which is used to wait on the vserver after it has been
406 stopped. Each option must be on a separate line. This file will be ignored when the
407 'sync' does not exist and the '--sync' option was not used.
411 <list name="cmd.prepare">
413 The command which is used to setup the init-system (e.g. to set the runlevel
414 in the utmp-file). Each option must be on a separate line.
418 <boolean name="sync">
420 If this file is not present, all 'cmd.*-sync files will be ignored.
426 A symlink to the TTY device where input/output will be redirected from/to
427 at startup via initscript.
433 This file is used to mark group of vservers which shall be started/stopped
434 together by the initscript. Content is a simple string like 'default'.
438 <list name="depends">
440 This file is used to configure vservers which must be running before the
441 current vserver can be started. At shutdown, the current vserver will be stopped before
442 its dependencies. Content of this file are vserver ids (one name per line).
447 <collection name="vshelper">
448 <scalar name="sync-timeout">
450 The timeout in seconds which is used when synchronising vserver startup/shutdown
451 with the vshelper. When no set, 30 seconds will be assumed.
453 <default>30</default>
456 <scalar name="action">
458 The action which is going to be executed when a vshelper event occurs. The
459 default value is 'restart', but there can be defined own methods by placing scripts into
460 the 'vshelper-methods' directories. These scripts are fed with the same arguments as the
463 <default>restart</default>
466 <program name="event" type="symbolic">
468 When existing. these scripts will be executed *instead* of the default
469 handler defined in 'action'. Their name must match the event which caused the execution
470 of 'vshelper'; e.g. 'restart' or 'poweroff'. See the vs_reboot() function in the kernel
474 <parameter name="xid">
475 <description>The xid of the context calling the vshelper</description>
477 <parameter name="event">
478 <description>The reboot-event</description>
483 <boolean name="disabled">
485 When existing, the vshelper functionality will be disabled for this
490 <boolean name="warning-disabled">
492 When existing, sanity checks for the vshelper functionality will be
497 <link name="logfile">
499 The file where output will be logged to when 'vshelper' is invoked from the
500 kernel. This should point somewhere e.g. into /var/log.
505 <collection name="vshelper-methods">
506 <program name="handler" type="symbolic">
513 <collection name="vunify">
515 This directory contains configuration data required for vserver
519 <list name="exclude">
521 Static list of excluded files. This list supports an rsync syntax: when a
522 file is prefixed by '+', it is a candidate for unification; when there is no prefix or a
523 '-' it will be excluded. Shell-wildcards are allowed for the filenames.
527 <link name="refserver.X" type="symbolic">
529 These are symlinks to the configuration directory
530 (e.g. CONFDIR/vservers/<id>) of a refserver. There may be multiple such symlinks
531 but they must be prefixed by 'refserver.' and will be processed in alphanumerical
538 <collection name="scripts">
540 A directory for scripts. By default, when one of these scripts will be executed,
541 the execution of defaultscripts (within .../.defaults/scripts) will be skipped. To execute
542 them nevertheless, the $DONT_SKIP_DEFAULTS environment variable must be set by one of the
543 in-shellcontext scripts (the non-executable ones).
546 <program name="prepre-start">
548 The scriptlet which will be executed before the network-interfaces are enabled
549 and the directories are mounted."
552 <parameter name="vserver-dir">
553 <description>The configuration directory of the current vserver.</description>
555 <parameter name="vserver-name">
556 <description>The name of the current vserver.</description>
558 <parameter name="action">
559 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
563 <collection name="prepre-start.d">
565 Repository of prepre-start like scripts
567 <program name="script" type="symbolic">
568 <description>See prepre-start.</description>
570 <parameter name="vserver-dir">
571 <description>The configuration directory of the current vserver.</description>
573 <parameter name="vserver-name">
574 <description>The name of the current vserver.</description>
576 <parameter name="action">
577 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
583 <program name="pre-start">
585 The scriptlet which will be executed after network-interfaces were enabled and
586 the directories mounted, but before the vserver itself has been started.
589 <parameter name="vserver-dir">
590 <description>The configuration directory of the current vserver.</description>
592 <parameter name="vserver-name">
593 <description>The name of the current vserver.</description>
595 <parameter name="action">
596 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
600 <collection name="pre-start.d">
602 Repository of pre-start like scripts
604 <program name="script" type="symbolic">
605 <description>See pre-start.</description>
607 <parameter name="vserver-dir">
608 <description>The configuration directory of the current vserver.</description>
610 <parameter name="vserver-name">
611 <description>The name of the current vserver.</description>
613 <parameter name="action">
614 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
621 <program name="post-start">
623 The scriptlet which will be executed after the vserver has been started.
626 <parameter name="vserver-dir">
627 <description>The configuration directory of the current vserver.</description>
629 <parameter name="vserver-name">
630 <description>The name of the current vserver.</description>
632 <parameter name="action">
633 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
637 <collection name="post-start.d">
639 Repository of post-start like scripts
641 <program name="script" type="symbolic">
642 <description>See post-start.</description>
644 <parameter name="vserver-dir">
645 <description>The configuration directory of the current vserver.</description>
647 <parameter name="vserver-name">
648 <description>The name of the current vserver.</description>
650 <parameter name="action">
651 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
658 <program name="pre-stop">
660 The scriptlet which will be executed before the vserver will be stopped.
663 <parameter name="vserver-dir">
664 <description>The configuration directory of the current vserver.</description>
666 <parameter name="vserver-name">
667 <description>The name of the current vserver.</description>
669 <parameter name="action">
670 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
674 <collection name="pre-stop.d">
676 Repository of pre-stop like scripts
678 <program name="script" type="symbolic">
679 <description>See pre-stop.</description>
681 <parameter name="vserver-dir">
682 <description>The configuration directory of the current vserver.</description>
684 <parameter name="vserver-name">
685 <description>The name of the current vserver.</description>
687 <parameter name="action">
688 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
694 <program name="post-stop">
696 The scriptlet which will be executed after the vserver has been stopped, but
697 before the directories will be umounted and the the interfaces
701 <parameter name="vserver-dir">
702 <description>The configuration directory of the current vserver.</description>
704 <parameter name="vserver-name">
705 <description>The name of the current vserver.</description>
707 <parameter name="action">
708 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
712 <collection name="post-stop.d">
714 Repository of post-stop like scripts
716 <program name="script" type="symbolic">
717 <description>See post-stop.</description>
719 <parameter name="vserver-dir">
720 <description>The configuration directory of the current vserver.</description>
722 <parameter name="vserver-name">
723 <description>The name of the current vserver.</description>
725 <parameter name="action">
726 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
732 <program name="postpost-stop">
734 The scriptlet which will be executed after the vserver has been stopped
738 <parameter name="vserver-dir">
739 <description>The configuration directory of the current vserver.</description>
741 <parameter name="vserver-name">
742 <description>The name of the current vserver.</description>
744 <parameter name="action">
745 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
749 <collection name="postpost-stop.d">
751 Repository of postpost-stop like scripts
753 <program name="script" type="symbolic">
754 <description>See postpost-stop.</description>
756 <parameter name="vserver-dir">
757 <description>The configuration directory of the current vserver.</description>
759 <parameter name="vserver-name">
760 <description>The name of the current vserver.</description>
762 <parameter name="action">
763 <description>The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).</description>
770 <collection name="interfaces">
771 <scalar name="bcast">
772 <description>The default broadcast address.</description>
775 <description>The default network device.</description>
777 <scalar name="prefix">
778 <description>The default network prefix-length.</description>
781 <description>The default network mask.</description>
783 <scalar name="scope">
784 <description>The default scope of the network interfaces.</description>
787 <collection name="iface" type="symbolic">
789 'iface' is an arbitrary name for the interface; the value itself is not important
790 but may be interesting regarding interface-creation and usage with 'chbind'. Both happens in
791 alphabetical order and numbers like '00' are good names for these directories.
794 <boolean name="disabled">
795 <description>When this file exists, this interface will be ignored.</description>
799 <description>The ip which will be assigned to this interface.</description>
801 <scalar name="bcast">
802 <description>The broadcast address.</description>
805 <description>The network device.</description>
807 <scalar name="prefix">
808 <description>The network prefix-length.</description>
811 <description>The network mask.</description>
813 <scalar name="scope">
814 <description>The scope of the network interface.</description>
818 When this file exists, the interface will be named
819 with the text in this file. Without such an entry,
820 the IP will not be shown by 'ifconfig' but by 'ip
821 addr ls' only. Such a labeled interface is known
822 as an "alias" also (e.g. 'eth0:foo').
825 <boolean name="nodev">
827 When this file exists, the interface will be
828 assumed to exist already. This can be used to
829 assign primary interfaces which are created by
830 the host or another vserver.
836 <collection name="ulimits">
838 A directory with ulimits. Possible resources are cpu, data, fsize, locks,
839 memlock, nofile, nproc, rss and/or stack. This configuration will be honored
842 <scalar name="resource" type="symbolic">
844 A file which contains the hard- and soft-limit of the given resource in the
845 first line. The special keyword 'inf' is recognized.
848 <scalar name="resource.hard" type="symbolic">
850 A file which contains the hard- of the given resource in the first line. The
851 special keyword 'inf' is recognized.
854 <scalar name="resource.soft" type="symbolic">
856 A file which contains the soft- of the given resource in the first line. The
857 special keyword 'inf' is recognized.
862 <collection name="rlimits">
864 A directory with resource limits. Possible resources are cpu, fsize, data, stack,
865 core, rss, nproc, nofile, memlock, as and locks. This configuration will be honored
868 <scalar name="resource" type="symbolic">
870 A file which contains the hard- and soft-limit of the given resource in the
871 first line. The special keyword 'inf' is recognized.
874 <scalar name="resource.hard" type="symbolic">
876 A file which contains the hard- of the given resource in the first line. The
877 special keyword 'inf' is recognized.
880 <scalar name="resource.soft" type="symbolic">
882 A file which contains the soft- of the given resource in the first line. The
883 special keyword 'inf' is recognized.
886 <scalar name="resource.min" type="symbolic">
888 A file which contains the guaranted minimum of the given resource in the first line. The
889 special keyword 'inf' is recognized.
894 <collection name="uts">
895 <scalar name="context">
897 The context-name of the vserver. This file is listed for completeness only;
898 the 'context' name is used and set internally by the util-vserver tools and can *not* be
902 <scalar name="sysname">
903 <description>The sysname of the vserver</description>
905 <scalar name="nodename">
906 <description>The node-/hostname of the vserver</description>
908 <scalar name="release">
909 <description>The OS-release of the vserver</description>
911 <scalar name="version">
912 <description>The OS-version of the vserver</description>
914 <scalar name="machine">
915 <description>The machine-type of the vserver</description>
917 <scalar name="domainname">
918 <description>The NIS domainname of the vserver</description>