1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE database SYSTEM "configuration.dtd" []>
5 <database xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
6 xsi:noNamespaceSchemaLocation="file:configuration.xsd">
8 <!-- Global configuration -->
9 <collection name=".defaults" use="optional">
10 <collection name="init" type="fixed">
12 <description>Default mtab file</description>
16 <link name="vdirbase">
17 <default>/vservers</default>
18 <description>A link to the default vserver rootdirectory.</description>
21 <link name="cachebase">
22 <default>/var/cache/vservers</default>
24 A link to the directory which will hold cached information about
29 <boolean id="global-nonamespace" name="nonamespace">
31 Disable namespace usage globally. It can be overridden for a single vserver
32 by setting the <optionref ref="global-namespace">namespace</optionref> flag
35 In this mode the <directory>/vservers</directory> directory must have
36 the 'barrier' attribute. Else, common chroot(2) exploits are possible.
40 <boolean id="global-nonamespace-cleanup" name="nonamespace-cleanup">
42 Disable namespace cleanup globally. It can be overridden for a single vserver
43 by setting the <optionref ref="namespace-cleanup">namespace-cleanup</optionref> flag
48 <list id="global-namespace-cleanup-skip" name="namespace-cleanup-skip">
50 List of paths to skip during namespace cleanup.
56 Path of the vserver run reverse directory. This directory contains
57 symlinks named with XID numbers which point back to the configuration
58 directory of vservers. Under kernel 2.4 this is required for the XID
59 to VSERVER mapping; Under kernel 2.6 it is unused.
61 NOTE: this link exists in 0.30.202+ only; in previous versions it was
62 a vserver specific setting.
68 Contains the pathname of the shell which will be used by the "vserver
69 ... enter" command. Can be overridden by the
70 <optionref ref="shell">per-guest shell</optionref>.
76 The default fstab file to put in newly built guests.
80 <boolean name="context.dynamic">
82 If this file exists, kernel-side dynamic contexts will be used by the "vserver
83 ... build" command. Otherwise a context will be generated, based on the
84 contents of <optionref>context.next</optionref>.
88 <scalar id="context.next" name="context.next">
90 The context id to use for the next guest created by "vserver ... build".
94 <collection name="apps">
95 <collection name="pkgmgmt">
97 <default>/vservers/.pkg</default>
99 <data name="apt.conf">
100 <description>The default apt.conf which is going to be used. It is overridden by
101 distribution specific configuration file.
106 <collection name="debootstrap">
107 <scalar name="mirror">
109 The Debian mirror to use with the <tool>debootstrap</tool> program
114 When the <tool>debootstrap</tool> package is not installed; fetch it
115 from this uri and install it at a temporary place.
120 <collection name="vdevmap">
121 <collection name="x" type="sybmolic">
122 <description>'x' is an arbitrary name, replace it with e.g. device names</description>
123 <boolean name="open">
124 <description>When this file exists, the device can be opened</description>
126 <boolean name="create">
127 <description>When this file exists, the device can be created (if the guest has <optionref ref="bcapabilities">CAP_MKNOD</optionref>)</description>
129 <boolean id="vdevmap-remap" name="remap">
131 When this file exists, <optionref ref="vdevmap-target">target</optionref> will
132 have to exist as well and opening the device will in fact open the target device
135 <scalar name="flags">
136 <description>This file will let you specify unimplemented flags manually</description>
138 <scalar name="device">
139 <description>Contains the name of a device node</description>
141 <scalar id="vdevmap-target" name="target">
142 <description>Contains the device node of the target node to open instead of the device when <optionref ref="vdevmap-remap">remap</optionref> is set</description>
147 <collection name="vshelper">
148 <link name="logfile">
150 The file where output will be logged to when <tool>vshelper</tool>
151 is invoked from the kernel. This should point somewhere e.g. into
152 <directory>/var/log</directory>.
156 <collection name="vshelper-methods">
157 <program name="handler" type="symbolic">
159 See <optionref ref="vshelper-action">vshelper/action</optionref>.
164 <boolean name="disabled">
166 When existing, the vshelper functionality will be disabled for all
171 <boolean name="debug">
173 When existing, the vshelper execution will be traced.
177 <boolean name="warning-disabled">
179 When existing, sanity checks for the vshelper functionality will be
186 <collection name="vprocunhide">
189 A list of files which will be made visible by vprocunhide. Wildcards are
190 allowed and anything ending in '/' will be processed recursively. When this file exists,
191 it overrides the defaults in SYSDEFAULTDIR/vprocunhide-files. The entries there must be
192 absolute filenames inclusive the leading '/proc'.
197 <collection name="init">
200 A symlink to the TTY device where input/output will be redirected from/to
201 at startup via initscript.
205 <hash id="global-environment" name="environment" since="0.30.211">
207 The environment to set when starting guests. Contains one VAR=VAL
213 <collection name="vunify">
214 <list name="exclude">
215 <description>Static list of excluded files.</description>
218 <collection name="hash" since="0.30.205">
220 A directory which will be used as the storage place for the
221 <tool>vhashify</tool> command.
223 <link name="id" type="symbolic">
225 Points to a directory within the filesystems which are used for the
226 vservers. There must be not more than one of such a directory per
231 <scalar name="method" since="0.30.299">
232 <default>SHA1</default>
233 <description>The used hash method.</description>
237 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205">
239 When existing, information from packagemanagement will not be used to
240 create dynamic exclude-lists.
244 <boolean name="pgkmgmt-force" default="off" since="0.30.205">
246 When existing, information from packagemanagement will be used to
247 create dynamic exclude-lists. This option requires that (a known)
248 packagemanagement is configured for the vserver; else the requested
249 operation will fail. Most tools assume 'on' as the default value.
255 <collection name="vlogin">
256 <boolean id="vlogin-disable" name="disable" since="0.30.212">
258 When this file exists, vlogin isn't used on vserver <guest> enter.
263 <collection name="build">
264 <list name="options">
266 A list of default options to supply to vserver ... build, one option per line.
272 <collection name="interfaces" use="optional">
273 <boolean id="global-vlandev" name="vlandev" since="0.30.211">
275 When this file exists, the steps which setup and destroy a VLAN
276 interface will be executed.
281 <collection name="files">
282 <description>This directory contains some files which will be copied to the guests during build.</description>
284 <description>The default /etc/hosts file.</description>
286 <data name="nsswitch.conf">
287 <description>The default /etc/nsswitch.conf file.</description>
289 <data name="krb5.conf">
290 <description>The default /etc/krb5.conf file.</description>
292 <data name="krb.conf">
293 <description>The default /etc/krb.conf file.</description>
295 <data name="krb.realms">
296 <description>The default /etc/krb.realms file.</description>
298 <data name="ldap.conf">
299 <description>The default /etc/ldap.conf file.</description>
301 <data name="localtime">
302 <description>The default /etc/localtime file.</description>
304 <data name="resolv.conf">
305 <description>The default /etc/resolv.conf file.</description>
309 <collection name="cgroup" use="optional" since="0.30.216" id="global-cgroup">
311 This directory contains cgroup settings which should be applied to all guests.
312 See your kernel documentation for what settings are valid with your
317 The directory to mount the cgroup hierarchy at. The default is /dev/cgroup.
320 <scalar name="subsys">
322 Comma-separated list of subsystems to enable on the cgroup mount point.
323 The default is "all".
326 <list name="inherit">
328 Some subsystems start out with clean slates, making it impossible to use the
329 cgroup before certain things have been set. This is true for e.g. the cpuset
330 subsystem. This file contains a list of filenames which should be explicitly
331 inherited from the parent (root) cgroup, if not overridden elsewhere.
332 The default is cpuset.cpus and cpuset.mems.
335 <scalar name="name" id="global-cgroup-name">
337 If this file exists, all guests will be put in one cgroup named after the
338 contents of this file. The default is to put each guest in a cgroup named the
339 same thing as the guest.
345 <collection name=".distributions" use="optional">
346 <collection name="dist" type="symbolic">
348 <description></description>
350 <collection name="yum">
352 The default, yum-related content of the <directory>/etc</directory>
355 <scalar name="yum.conf">
357 The master yum configuration file. It supports the @YUMETCDIR@,
358 @YUMCACHEDIR@ and @YUMLOGDIR@ placeholder which will be replaced at
359 <command>vserver ... build</command> time.
363 <collection name="yum.repos.d">
364 <description>A directory with yum repositories.</description>
366 <data name="apt.conf">
368 The default apt.conf which is going to be used. It overrides the
369 apt.conf from CONFDIR/.defaults/apps/pkgmgmt.
372 <program name="initpre">
374 Script which will be executed before packages will be installed.
377 <parameter name="confdir">
379 The configuration directory of the vserver which is going to be set up.
382 <parameter name="util-vserver-vars">
384 The pathname of the util-vserver-vars file.
389 <program name="initpost">
391 Script which will be executed after packages are installed.
394 <parameter name="confdir">
396 The configuration directory of the vserver which is going to be set up.
399 <parameter name="vserver">
401 The pathname of the util-vserver-vars file.
407 <collection name="pkgs">
409 Contains files with packagenames.
413 File which contains the name of packages. On top of file the special
414 keywords '--reinstall' and '--can-fail' are possible.
419 <collection name="pubkeys">
421 Directory with GPG pubkeys which are used to sign the packages of this
426 <collection name="apt">
428 Default content of the <directory>/etc/apt/</directory> directory.
432 <collection name="rpm">
434 Default content of the <directory>/etc/rpm</directory> directory.
440 Directory which overrides <directory>/usr/lib/rpm</directory>.
443 <link name="execdir">
445 Directory with all executables and libraries which are required for
450 <link name="template">
452 Symlink to the default template for this distribution.
457 <!-- Vserver configuration -->
458 <collection name="vserver-name" type="symbolic">
460 The configuration directory for the vserver vserver-name.
464 <default>../.defaults/cachebase/VSERVERNAME</default>
466 Path of the storage area for cached information about this vserver.
471 <default>../.defaults/vdirbase/VSERVERNAME</default>
473 Path of the vserver root directory.
479 Points to a file which will contain the XID of the running vserver. When
480 the vserver is stopped, this can be a dangling symlink.
484 <list id="bcapabilities" name="bcapabilities">
486 Contains the system capabilities. See
487 <ulink url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/bcaps-v13.c">lib/bcaps-v13.c</ulink>
491 <list name="ccapabilities">
493 Contains the context capabilities. See <ulink
494 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/ccaps-v13.c">lib/ccaps-v13.c</ulink>
498 <list name="ncapabilities" since="0.30.212">
500 Contains the network capabilities. See <ulink
501 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/ncaps-net.c">lib/ncaps-net.c</ulink>
506 <boolean id="global-namespace" name="namespace">
508 Overrides the global <optionref ref="global-nonamespace">nonamespace</optionref> flag and enables
509 namespace usage for the current vserver.
513 <boolean name="nonamespace">
515 Disables namespace usage for the current vserver.
517 In this mode the <directory>/vservers</directory> directory must have
518 the 'barrier' attribute. Else, common chroot(2) exploits are possible.
522 <boolean id="namespace-cleanup" name="namespace-cleanup">
524 Overrides the global <optionref ref="global-nonamespace-cleanup">nonamespace-cleanup</optionref> flag and enables
525 namespace cleanup for the current vserver.
529 <list name="namespace-cleanup-skip">
531 List of paths to skip during namespace cleanup. This overrides the global
532 <optionref ref="global-namespace-cleanup-skip">namespace-cleanup-skip</optionref>
537 <hash name="schedule">
539 [deprecated; use <optionref ref="sched">sched</optionref> instead] Contains the
540 scheduler parameters, one per line.
542 The Hard CPU limit uses a mechanism called a Token Bucket. the
543 concept is simple: you have a bucket of a certain size which is
544 filled with a specified amount R of tokens each interval T until the
545 maximum is reached (excess tokens are spilled). At each timer tick,
546 a running process consumes one token from the bucket, unless the
547 bucket is empty. If the bucket is empty the process is put in the
548 hold queue. When the bucket has been refilled to at least M tokens,
549 all on hold processes are rescheduled.
551 See the <ulink url="http://linux-vserver.org/Scheduler+Parameters">Linux
552 VServer Wiki</ulink> for more information about this file.
555 <key id="fill_rate" name="fill-rate">
557 Amount of tokens append to the bucket each interval.
560 <key name="interval">
562 The intervall between refills of amount <optionref>fill_rate</optionref>. This
563 value is express in ticks.
568 Initial bucket contents.
571 <key name="tokens-min">
573 The minimum amount of tokens required to unhold processes
576 <key name="tokens-max">
581 <key name="priority-bias">
590 Contains the name of the vserver. When not given, the basename of the directory
591 will be assumed as this name.
596 The nice-level on which the vserver will be started.
599 <list name="capabilities">
601 Contains per line a capability. This file is used for the 2.4 kernel
602 only; for 2.6 use <optionref>bcapabilities</optionref>.
605 <scalar id="shell" name="shell">
607 Contains the pathname of the shell which will be used by the "vserver
611 <list name="personality">
613 Used to set the personality of the vserver. First line in the file
614 is the personality-type followed by flags (one item per line). See
615 <filename>/usr/include/linux/personality.h</filename> for possible
621 Contains per line a flag. See <ulink
622 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/cflags-v13.c">lib/cflags-v13.c</ulink>
627 <element name="fakeinit">
629 The new process will believe it is process number 1. Useful to run a
630 real /sbin/init in a vserver. Warning: this flag should not be used
631 unless you know what you are doing. Often, it is better to use the
635 <element name="lock">
637 The new process is trapped and can't use chcontext anymore.
640 <element name="sched">
642 The new process and its children will share a common
645 <element name="nproc">
647 Limit the number of process in the vserver according to
648 ulimit setting. Normally, ulimit is a per user thing.
649 With this flag, it becomes a per vserver thing.
652 <element name="private">
654 No one can join this security context once created.
657 <element name="ulimit">
659 Apply the current ulimit to the whole context
665 <list name="nflags" since="0.30.212">
667 Contains a network flag per line. See <ulink
668 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/nflags-net.c">lib/nflags-net.c</ulink>
672 <scalar name="context">
674 Contains the context id which shall be used for the vserver. Valid range is 2 through 49151.
677 <scalar name="ncontext">
679 Contains the network context id which shall be used for the vserver. Valid range is 2 through 49151.
684 Contains the filesystem tag which shall be used for the vserver. Valid range is 2 through 49151.
687 <data id="fstab" name="fstab">
689 The fstab file for the vserver. Entries in this file will be mounted
690 within the network context of the host. Use the
691 <optionref>fstab.remote</optionref> file when you want that the
692 mounting happens in the network context of the vserver. In most cases
693 the 'fstab' file should be used.
696 <data id="fstab.remote" name="fstab.remote">
698 The fstab file for the vserver. Entries in this file will be mounted
699 within the network context of the guest; this means that mount will be
700 called as <command>chbind <options> mount ...</command>. See
701 <optionref>fstab</optionref> also.
704 <scalar name="badness">
706 Contains the bias to be applied to processes in this guest when the OOM-killer strikes.
710 <collection name="apps">
711 <collection name="init">
714 The initial-mtab which will be used for the vserver.
718 <scalar name="style">
720 Contains the init-style.
723 <enumeration value="sysv"/>
724 <enumeration value="plain"/>
725 <enumeration value="minit"/>
729 <scalar name="runlevel">
730 <description>The start runlevel.</description>
733 <scalar name="runlevel.start">
734 <description>The start runlevel.</description>
737 <scalar name="runlevel.stop">
738 <description>The stop runlevel.</description>
741 <scalar name="killseq">
743 Contains the 'signal [wait signal]*' sequence which is used to stop
748 <list name="cmd.start">
750 The command which is used to start the vserver. Each option must be on
755 <list name="cmd.start-sync">
757 The command which is used to wait on the vserver after it has been
758 started. Each option must be on a separate line. This file will be
759 ignored when the <optionref>sync</optionref> flag does not exist and the
760 '--sync' option was not used.
764 <list name="cmd.stop">
766 The command which is used to stop the vserver. Each option must be on
771 <list name="cmd.stop-sync">
773 The command which is used to wait on the vserver after it has been
774 stopped. Each option must be on a separate line. This file will be
775 ignored when the <optionref>sync</optionref> flag does not exist and the
776 '--sync' option was not used.
780 <list name="cmd.prepare">
782 The command which is used to setup the init-system (e.g. to set the
783 runlevel in the utmp-file). Each option must be on a separate line.
787 <boolean id="sync" name="sync">
789 If this file is not present, all 'cmd.*-sync files will be ignored.
795 A symlink to the TTY device where input/output will be redirected
796 from/to at startup via initscript.
802 This file is used to mark group of vservers which shall be started/stopped
803 together by the initscript. Content is a simple string like 'default'.
807 <list name="depends">
809 This file is used to configure vservers which must be running before
810 the current vserver can be started. At shutdown, the current vserver
811 will be stopped before its dependencies. Content of this file are
812 vserver ids (one name per line).
816 <hash name="environment" since="0.30.211">
818 The environment to set when starting the guest. Contains one VAR=VAL
824 <collection name="vdevmap">
825 <collection name="x" type="sybmolic">
826 <description>'x' is an arbitrary name, replace it with e.g. device names</description>
827 <boolean name="open">
828 <description>When this file exists, the device can be opened</description>
830 <boolean name="create">
831 <description>When this file exists, the device can be created (if the guest has <optionref ref="bcapabilities">CAP_MKNOD</optionref>)</description>
833 <boolean id="guest-vdevmap-remap" name="remap">
835 When this file exists, <optionref ref="guest-vdevmap-target">target</optionref> will
836 have to exist as well and opening the device will in fact open the target device
839 <scalar name="flags">
840 <description>This file will let you specify unimplemented flags manually</description>
842 <scalar name="device">
843 <description>Contains the name of a device node</description>
845 <scalar id="guest-vdevmap-target" name="target">
846 <description>Contains the device node of the target node to open instead of the device when <optionref ref="guest-vdevmap-remap">remap</optionref> is set</description>
851 <collection name="vshelper">
852 <scalar name="sync-timeout">
853 <default>30</default>
855 The timeout in seconds which is used when synchronising vserver
856 startup/shutdown with the vshelper. When not set, 30 seconds will be
861 <scalar id="vshelper-action" name="action">
862 <default>restart</default>
864 The action which is going to be executed when a vshelper event
865 occurs. The default value is 'restart', but there can be defined own
866 methods by placing scripts into the
867 <optionref>vshelper-methods</optionref> directories. These scripts are
868 fed with the same arguments as the <tool>vshelper</tool> script.
872 <program name="event" type="symbolic">
874 When existing, these scripts will be executed *instead* of the default
875 handler defined in 'action'. Their name must match the event which caused
876 the execution of <tool>vshelper</tool>; e.g. 'restart' or 'poweroff'. See
877 the vs_reboot() function in the kernel for more details.
880 <parameter name="xid">
882 The xid of the context calling the vshelper
885 <parameter name="event">
893 <boolean name="disabled">
895 When existing, the vshelper functionality will be disabled for this
900 <boolean name="debug">
902 When existing, the vshelper execution will be traced for this vserver.
906 <boolean name="warning-disabled">
908 When existing, sanity checks for the vshelper functionality will be
915 <collection id="vshelper-methods" name="vshelper-methods">
916 <program name="handler" type="symbolic">
918 See <optionref ref="vshelper-action">vshelper/action</optionref>.
923 <collection name="vunify">
925 This directory contains configuration data required for vserver
929 <list name="exclude">
931 <p>Static list of files which are excluded for unification. This list
932 supports an rsync-like syntax: when a file is prefixed by '+', it is a
933 candidate for unification; when there is no prefix or a '-' or a '~' it
934 will be excluded. Shell-wildcards are allowed for the filenames.</p>
935 <p>When used with <tool>vcopy</tool>, the '~' prefix prevents copying
936 of the file entirely (e.g. for keyfiles). With this tool, the file will
937 be copied instead of hardlinked when the '-' prefix is used.</p>
941 <link name="refserver.X" type="symbolic">
943 These are symlinks to the configuration directory
944 (e.g. CONFDIR/vservers/<id>) of a refserver. There may be
945 multiple such symlinks but they must be prefixed by 'refserver.' and
946 will be processed in alphanumerical order.
950 <collection name="hash" since="0.30.205">
952 A directory which will be used as the storage place for the
953 <tool>vhashify</tool> command.
955 <link name="id" type="symbolic">
957 Points to a directory within the filesystems which are used for the
958 vservers. There must be not more than one of such a directory per
963 <scalar name="method" since="0.30.299">
964 <default>SHA1</default>
965 <description>The used hash method.</description>
969 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205">
971 When existing, information from packagemanagement will not be used to
972 create dynamic exclude-lists.
976 <boolean name="pgkmgmt-force" default="off" since="0.30.205">
978 When existing, information from packagemanagement will be used to
979 create dynamic exclude-lists. This option requires that (a known)
980 packagemanagement is configured for the vserver; else the requested
981 operation will fail. Most tools assume 'on' as the default value.
988 <collection name="scripts">
990 A directory for scripts. By default, when one of these scripts will be
991 executed, the execution of defaultscripts (within .../.defaults/scripts)
992 will be skipped. To execute them nevertheless, the $DONT_SKIP_DEFAULTS
993 environment variable must be set by one of the in-shellcontext scripts
994 (the non-executable ones).
997 <program name="initialize" since="0.30.211">
999 The scriptlet which will be executed before the root filesystem is mounted and
1000 the configuration has been loaded. Before executing the script, the
1001 configuration directory will be made the working directory.
1004 <parameter name="action">
1006 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1009 <parameter name="vserver-name">
1011 The name of the current vserver.
1016 <collection name="initialize.d" since="0.30.211">
1018 Repository of initialize like scripts. Before executing the script,
1019 the configuration directory will be made the working directory.
1021 <program name="script" type="symbolic">
1022 <description>See initialize.</description>
1024 <parameter name="action">
1026 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1029 <parameter name="vserver-name">
1031 The name of the current vserver.
1038 <program name="prepre-start">
1040 The scriptlet which will be executed before the network-interfaces are
1041 enabled and the directories are mounted. Before executing the script,
1042 the configuration directory will be made the working directory.
1045 <parameter name="action">
1047 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1050 <parameter name="vserver-name">
1052 The name of the current vserver.
1057 <collection name="prepre-start.d">
1059 Repository of prepre-start like scripts. Before executing the script,
1060 the configuration directory will be made the working directory.
1062 <program name="script" type="symbolic">
1063 <description>See prepre-start.</description>
1065 <parameter name="action">
1067 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1070 <parameter name="vserver-name">
1072 The name of the current vserver.
1079 <program name="pre-start">
1081 The scriptlet which will be executed after network-interfaces were
1082 enabled and the directories mounted, but before the vserver itself has
1083 been started. Before executing the script, the vserver root directory
1084 will be made the working directory.
1087 <parameter name="action">
1089 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1092 <parameter name="vserver-name">
1094 The name of the current vserver.
1099 <collection name="pre-start.d">
1101 Repository of pre-start like scripts. Before executing these scripts,
1102 the vserver root directory will be made the working directory.
1104 <program name="script" type="symbolic">
1105 <description>See pre-start.</description>
1107 <parameter name="action">
1109 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1112 <parameter name="vserver-name">
1114 The name of the current vserver.
1122 <program name="post-start">
1124 The scriptlet which will be executed after the vserver has been
1125 started. Before executing the script, the vserver root directory
1126 will be made the working directory.
1129 <parameter name="action">
1131 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1134 <parameter name="vserver-name">
1136 The name of the current vserver.
1141 <collection name="post-start.d">
1143 Repository of post-start like scripts. Before executing these scripts,
1144 the vserver root directory will be made the working directory.
1146 <program name="script" type="symbolic">
1147 <description>See post-start.</description>
1149 <parameter name="action">
1151 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1154 <parameter name="vserver-name">
1156 The name of the current vserver.
1164 <program name="pre-stop">
1166 The scriptlet which will be executed before the vserver will be
1167 stopped. Before executing the script, the vserver root directory
1168 will be made the working directory.
1171 <parameter name="action">
1173 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1176 <parameter name="vserver-name">
1178 The name of the current vserver.
1183 <collection name="pre-stop.d">
1185 Repository of pre-stop like scripts. Before executing the script, the
1186 vserver root directory will be made the working directory.
1188 <program name="script" type="symbolic">
1189 <description>See pre-stop.</description>
1191 <parameter name="action">
1193 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1196 <parameter name="vserver-name">
1198 The name of the current vserver.
1205 <program name="post-stop">
1207 The scriptlet which will be executed after the vserver has been
1208 stopped, but before the directories will be umounted and the the
1209 interfaces disabled. Before executing the script, the vserver root
1210 directory will be made the working directory.
1213 <parameter name="action">
1215 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1218 <parameter name="vserver-name">
1220 The name of the current vserver.
1225 <collection name="post-stop.d">
1227 Repository of post-stop like scripts. Before executing the script, the
1228 vserver root directory will be made the working directory.
1230 <program name="script" type="symbolic">
1231 <description>See post-stop.</description>
1233 <parameter name="action">
1235 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1238 <parameter name="vserver-name">
1240 The name of the current vserver.
1247 <program name="postpost-stop">
1249 The scriptlet which will be executed after the vserver has been stopped
1250 completely. Before executing the script, the vserver root directory
1251 will be made the working directory.
1254 <parameter name="action">
1256 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1259 <parameter name="vserver-name">
1261 The name of the current vserver.
1266 <collection name="postpost-stop.d">
1268 Repository of postpost-stop like scripts. Before executing the script,
1269 the vserver root directory will be made the working directory.
1271 <program name="script" type="symbolic">
1272 <description>See postpost-stop.</description>
1274 <parameter name="action">
1276 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1279 <parameter name="vserver-name">
1281 The name of the current vserver.
1289 <collection name="interfaces">
1290 <scalar name="bcast">
1291 <description>The guest's broadcast address.</description>
1293 <scalar name="lback">
1294 <description>The guest's loopback address.</description>
1297 <description>The default network device. See <optionref ref="per-if-dev">iface/dev</optionref> for more information.</description>
1299 <scalar name="prefix">
1300 <description>The default network prefix-length.</description>
1302 <scalar name="mask">
1303 <description>The default network mask.</description>
1305 <scalar name="scope">
1306 <description>The default scope of the network interfaces.</description>
1308 <boolean id="local-vlandev" name="vlandev" since="0.30.211">
1310 When this file exists, the steps which setup and destroy a VLAN
1311 interface will be executed for all interfaces of this vserver.
1314 <boolean id="local-novlandev" name="novlandev">
1316 When this file exists, the steps which setup and destroy a VLAN
1317 interface will be skipped. This overrides the global
1318 <optionref ref="global-vlandev">vlandev</optionref> setting for
1323 <collection name="iface" type="symbolic">
1325 'iface' is an arbitrary name for the interface; the value itself is
1326 not important but may be interesting regarding interface-creation and
1327 usage with <tool>chbind</tool>. Both happens in alphabetical order and
1328 numbers like '00' are good names for these directories.
1331 <boolean name="disabled">
1332 <description>When this file exists, this interface will be ignored.</description>
1336 <description>The IP address which will be assigned to this interface.</description>
1338 <scalar name="dev" id="per-if-dev">
1339 <description>The network device. When this is specified, the IP address will be assigned and removed when starting and stopping the guest.</description>
1341 <scalar name="prefix">
1342 <description>The network prefix-length.</description>
1344 <scalar name="mask">
1345 <description>The network mask.</description>
1347 <scalar name="scope">
1348 <description>The scope of the network interface.</description>
1350 <scalar name="name">
1352 When this file exists, the interface will be named with the text in
1353 this file. Without such an entry, the IP will not be shown by
1354 <tool>ifconfig</tool> but by <command>ip addr ls</command> only. Such
1355 a labeled interface is known as an "alias" also (e.g. 'eth0:foo').
1358 <boolean name="nodev">
1360 When this file exists, the interface will be assumed to exist
1361 already. This can be used to assign primary interfaces which are
1362 created by the host or another vserver.
1365 <boolean name="novlandev">
1367 When this file exists, the steps which setup and destroy a VLAN
1368 interface will be skipped. This will override the global
1369 <optionref ref="global-vlandev">vlandev</optionref> and the per-guest
1370 <optionref ref="local-vlandev">vlandev</optionref>.
1373 <boolean name="vlandev" since="0.30.211">
1375 When this file exists, the steps which setup and destroy a VLAN
1376 interface will be executed.
1379 <boolean name="tun" since="0.30.215">
1381 When this file exists, a tun interface will be created when the guest
1382 starts, and removed when the guest stops.
1385 <boolean name="tap" since="0.30.215">
1387 When this file exists, a tap interface will be created when the guest
1388 starts, and removed when the guest stops.
1391 <boolean name="nocsum" since="0.30.215">
1393 If a tun or tap interface is created, the presence of this file will
1394 disable checksumming on it.
1397 <boolean name="shared" since="0.30.215">
1399 When this file exists, the tun/tap interface created will not be
1400 owned by this particular guest.
1403 <scalar name="uid" since="0.30.215">
1405 Sets the ownership of tun/tap interfaces. Requires a user id, not a
1409 <scalar name="gid" since="0.30.215">
1411 Sets the group ownership of tun/tap interfaces. Requires a group id,
1415 <scalar name="linktype" since="0.30.215">
1417 Sets the link type of tun/tap interfaces.
1420 <scalar name="peer" since="0.30.216">
1422 Sets the peer for a point-to-point link, such as a tun interface.
1428 <collection name="ulimits">
1430 A directory with ulimits. Possible resources are cpu, data, fsize,
1431 locks, memlock, nofile, nproc, rss and/or stack.
1433 <scalar name="resource" type="symbolic">
1435 A file which contains the hard- and soft-limit of the given resource
1436 in the first line. The special keyword 'inf' is recognized.
1439 <scalar name="resource.hard" type="symbolic">
1441 A file which contains the hard-limit of the given resource in the first
1442 line. The special keyword 'inf' is recognized.
1445 <scalar name="resource.soft" type="symbolic">
1447 A file which contains the soft-limit of the given resource in the first
1448 line. The special keyword 'inf' is recognized.
1453 <collection name="rlimits">
1455 A directory with resource limits. Possible resources are cpu, fsize,
1456 data, stack, core, rss, nproc, nofile, memlock, as, locks, msgqueue,
1457 nsock, openfd, anon, shmem, semary, nsems and dentry. This
1458 configuration will be honored for kernel 2.6 only.
1460 <scalar name="resource" type="symbolic">
1462 A file which contains the hard- and soft-limit of the given resource
1463 in the first line. The special keyword 'inf' is recognized.
1466 <scalar name="resource.hard" type="symbolic">
1468 A file which contains the hard-limit of the given resource in the first
1469 line. The special keyword 'inf' is recognized.
1472 <scalar name="resource.soft" type="symbolic">
1474 A file which contains the soft-limit of the given resource in the first
1475 line. The special keyword 'inf' is recognized.
1478 <scalar name="resource.min" type="symbolic">
1480 A file which contains the guaranteed minimum of the given resource in
1481 the first line. The special keyword 'inf' is recognized.
1486 <collection name="uts">
1487 <scalar name="context">
1489 The context-name of the vserver. This file is listed for completeness
1490 only; the 'context' name is used and set internally by the util-vserver
1491 tools and can *not* be modified.
1494 <scalar name="sysname">
1495 <description>The sysname of the vserver</description>
1497 <scalar name="nodename">
1498 <description>The node-/hostname of the vserver</description>
1500 <scalar name="release">
1501 <description>The OS-release of the vserver</description>
1503 <scalar name="version">
1504 <description>The OS-version of the vserver</description>
1506 <scalar name="machine">
1507 <description>The machine-type of the vserver</description>
1509 <scalar name="domainname">
1510 <description>The NIS domainname of the vserver</description>
1514 <collection name="dlimits" since="0.30.210">
1516 Note that all entries are required for the disk limit to be applied.
1518 <collection name="x" type="symbolic">
1519 <description>'x' is an arbitrary name, replace it with e.g. integers</description>
1520 <scalar name="directory">
1521 <description>The directory to which the limit should be applied</description>
1523 <scalar name="inodes_total">
1524 <description>The amount of inodes this vserver should be limited to</description>
1526 <scalar name="space_total">
1527 <description>The amount of space this vserver should be limited to (measured in blocks of 1024 bytes)</description>
1529 <scalar name="reserved">
1530 <description>How much space (percentage-wise) should be reserved for the root user</description>
1535 <collection name="sysctl" since="0.30.213">
1536 <collection name="x" type="symbolic">
1537 <description>'x' is an arbitrary name, replace it with e.g. integers</description>
1538 <scalar name="setting">
1539 <description>The sysctl setting</description>
1541 <scalar name="value">
1542 <description>The value</description>
1547 <collection name="cpuset" since="0.30.211">
1549 Puts the guest in a cpuset. Required entries are name, cpus and mems.
1551 <scalar name="name">
1552 <description>The name of the cpuset for this vserver</description>
1554 <scalar name="cpus">
1555 <description>The list of CPUs in this cpuset</description>
1557 <scalar name="mems">
1558 <description>The list of Memory Nodes in this cpuset</description>
1560 <scalar name="cpu_exclusive">
1561 <description>Is the CPU assignment exclusive?</description>
1563 <scalar name="mems_exclusive">
1564 <description>Is the memory node assignment exclusive?</description>
1566 <scalar name="nocreate">
1567 <description>When this file exists, the cpuset will be assumed to exist already</description>
1571 <collection id="sched" name="sched" since="0.30.212">
1572 <scalar id="global-tokens" name="tokens">
1573 <description>The initial amount of tokens to put in the bucket</description>
1575 <scalar id="global-tokens-min" name="tokens-min">
1576 <description>The minimum amount of tokens required to unhold the context</description>
1578 <scalar id="global-tokens-max" name="tokens-max">
1579 <description>The bucket's size</description>
1581 <scalar id="global-fill-rate" name="fill-rate">
1582 <description>Amount of tokens to add each <optionref ref="global-interval">interval</optionref></description>
1584 <scalar id="global-interval" name="interval">
1585 <description>The interval between refills of the bucket</description>
1587 <scalar id="global-priority-bias" name="priority-bias">
1588 <description>Bias added to priorities calculated within the guest (result is clamped to -20/+19)</description>
1590 <scalar id="global-fill-rate2" name="fill-rate2">
1591 <description>Amount of tokens to add each <optionref ref="global-interval2">interval2</optionref> when advancing idle time</description>
1593 <scalar id="global-interval2" name="interval2">
1594 <description>The interval between refills of the bucket when advancing idle time</description>
1596 <boolean id="global-idle-time" name="idle-time">
1597 <description>When this file exists, advancing idle time is activated</description>
1599 <collection name="cpu-id" type="symbolic">
1600 <description>This directory contains per-CPU and/or per-bucket specific settings. Remember to set the <optionref ref="cpu-id">cpu-id</optionref> file. All CPUs inherit the global settings.</description>
1601 <scalar name="tokens">
1602 <description>The initial amount of tokens to put in the bucket</description>
1604 <scalar name="tokens-min">
1605 <description>The minimum amount of tokens required to unhold the context</description>
1607 <scalar name="tokens-max">
1608 <description>The bucket's size</description>
1610 <scalar name="fill-rate">
1611 <description>Amount of tokens to add each <optionref ref="local-interval">interval</optionref></description>
1613 <scalar id="local-interval" name="interval">
1614 <description>The interval between refills of the bucket</description>
1616 <scalar name="priority-bias">
1617 <description>Bias added to priorities calculated within the guest (result is clamped to -20/+19)</description>
1619 <scalar name="fill-rate2">
1620 <description>Amount of tokens to add each <optionref ref="local-interval2">interval2</optionref> when advancing idle time</description>
1622 <scalar id="local-interval2" name="interval2">
1623 <description>The interval between refills of the bucket when advancing idle time</description>
1625 <boolean name="idle-time">
1626 <description>When this file exists, advancing idle time is activated</description>
1628 <scalar id="cpu-id" name="cpu-id">
1629 <description>The CPU to apply these settings to</description>
1631 <scalar name="bucket-id">
1632 <description>The bucket to apply these settings to</description>
1637 <collection name="spaces" since="0.30.215">
1638 <boolean name="pid">
1639 <description>Enables pid virtualization for this guest</description>
1641 <boolean name="net">
1642 <description>Enable network virtualization for this guest</description>
1644 <scalar name="mask">
1645 <description>Contains a mask of spaces to clone/enter</description>
1649 <collection name="ionice" since="0.30.216">
1650 <scalar name="class">
1651 <description>The IO scheduling class to use for this guest (see ionice(1)).</description>
1653 <scalar name="priority">
1654 <description>The IO scheduling priority to use for this guest (see ionice(1)).</description>
1658 <collection name="cgroup" use="optional" since="0.30.216" id="guest-cgroup">
1660 This directory contains cgroup settings to be applied to this guest.
1661 See your kernel documentation for what settings are valid with your
1664 <scalar name="name">
1666 If this file exists, the guest will be put in a cgroup named after the
1667 contents of this file. The default is to name the cgroup the same thing as the
1669 <optionref ref="global-cgroup-name">.defaults/cgroup/name</optionref> says
1674 <scalar name="nocgroup" since="0.30.216">
1676 If this file exists,
1677 <optionref ref="global-cgroup">.defaults/cgroup</optionref> will be ignored