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.
66 <collection name="apps">
67 <collection name="pkgmgmt">
69 <default>/vservers/.pkg</default>
71 <data name="apt.conf">
72 <description>The default apt.conf which is going to be used. It is overridden by
73 distribution specific configuration file.
78 <collection name="debootstrap">
79 <scalar name="mirror">
81 The Debian mirror to use with the <tool>debootstrap</tool> program
86 When the <tool>debootstrap</tool> package is not installed; fetch it
87 from this uri and install it at a temporary place.
92 <collection name="vshelper">
95 The file where output will be logged to when <tool>vshelper</tool>
96 is invoked from the kernel. This should point somewhere e.g. into
97 <directory>/var/log</directory>.
101 <collection name="vshelper-methods">
102 <program name="handler" type="symbolic">
109 <boolean name="disabled">
111 When existing, the vshelper functionality will be disabled for all
116 <boolean name="debug">
118 When existing, the vshelper execution will be traced.
122 <boolean name="warning-disabled">
124 When existing, sanity checks for the vshelper functionality will be
131 <collection name="vprocunhide">
134 A list of files which will be made visible by vprocunhide. Wildcards are
135 allowed and anything ending in '/' will be processed recursively. When this file exists,
136 it overrides the defaults in SYSDEFAULTDIR/vprocunhide-files. The entries there must be
137 absolute filenames inclusive the leading '/proc'.
142 <collection name="init">
145 A symlink to the TTY device where input/output will be redirected from/to
146 at startup via initscript.
150 <hash id="global-environment" name="environment" since="0.30.211">
152 The environment to set when starting guests. Contains one VAR=VAL
158 <collection name="vunify">
159 <list name="exclude">
160 <description>Static list of excluded files.</description>
163 <collection name="hash" since="0.30.205">
165 A directory which will be used as the storage place for the
166 <tool>vhashify</tool> command.
168 <link name="id" type="symbolic">
170 Points to a directory within the filesystems which are used for the
171 vservers. There must be not more than one of such a directory per
176 <scalar name="method" since="0.30.299">
177 <default>SHA1</default>
178 <description>The used hash method.</description>
182 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205">
184 When existing, information from packagemanagement will not be used to
185 create dynamic exclude-lists.
189 <boolean name="pgkmgmt-force" default="off" since="0.30.205">
191 When existing, information from packagemanagement will be used to
192 create dynamic exclude-lists. This option requires that (a known)
193 packagemanagement is configured for the vserver; else the requested
194 operation will fail. Most tools assume 'on' as the default value.
200 <collection name="vlogin">
201 <boolean id="vlogin-disable" name="disable" since="0.30.212">
203 When this file exists, vlogin isn't used on vserver <guest> enter.
209 <collection name="interfaces" use="optional">
210 <boolean id="global-vlandev" name="vlandev" since="0.30.211">
212 When this file exists, the steps which setup and destroy a VLAN
213 interface will be executed.
219 <collection name=".distributions" use="optional">
220 <collection name="dist" type="symbolic">
222 <description></description>
224 <collection name="yum">
226 The default, yum-related content of the <directory>/etc</directory>
229 <scalar name="yum.conf">
231 The master yum configuration file. It supports the @YUMETCDIR@,
232 @YUMCACHEDIR@ and @YUMLOGDIR@ placeholder which will be replaced at
233 <command>vserver ... build</command> time.
237 <collection name="yum.repos.d">
238 <description>A directory with yum repositories.</description>
240 <data name="apt.conf">
242 The default apt.conf which is going to be used. It overrides the
243 apt.conf from CONFDIR/.defaults/apps/pkgmgmt.
246 <program name="initpre">
248 Script which will be executed before packages will be installed.
251 <parameter name="confdir">
253 The configuration directory of the vserver which is going to be set up.
256 <parameter name="util-vserver-vars">
258 The pathname of the util-vserver-vars file.
263 <program name="initpost">
265 Script which will be executed after packages are installed.
268 <parameter name="confdir">
270 The configuration directory of the vserver which is going to be set up.
273 <parameter name="vserver">
275 The pathname of the util-vserver-vars file.
281 <collection name="pkgs">
283 Contains files with packagenames.
287 File which contains the name of packages. On top of file the special
288 keywords '--reinstall' and '--can-fail' are possible.
293 <collection name="pubkeys">
295 Directory with GPG pubkeys which are used to sign the packages of this
300 <collection name="apt">
302 Default content of the <directory>/etc/apt/</directory> directory.
306 <collection name="rpm">
308 Default content of the <directory>/etc/rpm</directory> directory.
314 Directory which overrides <directory>/usr/lib/rpm</directory>.
317 <link name="execdir">
319 Directory with all executables and libraries which are required for
326 <!-- Vserver configuration -->
327 <collection name="vserver-name" type="symbolic">
329 The configuration directory for the vserver vserver-name.
333 <default>../.defaults/cachebase/VSERVERNAME</default>
335 Path of the storage area for cached information about this vserver.
340 <default>../.defaults/vdirbase/VSERVERNAME</default>
342 Path of the vserver root directory.
348 Points to a file which will contain the XID of the running vserver. When
349 the vserver is stopped, this can be a dangling symlink.
353 <list id="bcapabilities" name="bcapabilities">
355 Contains the system capabilities. See
356 <ulink url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/bcaps-v13.c">lib/bcaps-v13.c</ulink>
360 <list name="ccapabilities">
362 Contains the context capabilities. See <ulink
363 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/ccaps-v13.c">lib/ccaps-v13.c</ulink>
367 <list name="ncapabilities" since="0.30.212">
369 Contains the network capabilities. See <ulink
370 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/ncaps-net.c">lib/ncaps-net.c</ulink>
375 <boolean id="global-namespace" name="namespace">
377 Overrides the global <optionref ref="global-nonamespace">nonamespace</optionref> flag and enables
378 namespace usage for the current vserver.
382 <boolean name="nonamespace">
384 Disables namespace usage for the current vserver.
386 In this mode the <directory>/vservers</directory> directory must have
387 the 'barrier' attribute. Else, common chroot(2) exploits are possible.
391 <boolean id="namespace-cleanup" name="namespace-cleanup">
393 Overrides the global <optionref ref="global-nonamespace-cleanup">nonamespace-cleanup</optionref> flag and enables
394 namespace cleanup for the current vserver.
398 <list name="namespace-cleanup-skip">
400 List of paths to skip during namespace cleanup. This overrides the global
401 <optionref ref="global-namespace-cleanup-skip">namespace-cleanup-skip</optionref>
406 <hash name="schedule">
408 [deprecated; use <optionref ref="sched">sched</optionref> instead] Contains the
409 scheduler parameters, one per line.
411 The Hard CPU limit uses a mechanism called a Token Bucket. the
412 concept is simple: you have a bucket of a certain size which is
413 filled with a specified amount R of tokens each interval T until the
414 maximum is reached (excess tokens are spilled). At each timer tick,
415 a running process consumes one token from the bucket, unless the
416 bucket is empty. If the bucket is empty the process is put in the
417 hold queue. When the bucket has been refilled to at least M tokens,
418 all on hold processes are rescheduled.
420 See the <ulink url="http://linux-vserver.org/Scheduler+Parameters">Linux
421 VServer Wiki</ulink> for more information about this file.
424 <key id="fill_rate" name="fill-rate">
426 Amount of tokens append to the bucket each interval.
429 <key name="interval">
431 The intervall between refills of amount <optionref>fill_rate</optionref>. This
432 value is express in ticks.
437 Initial bucket contents.
440 <key name="tokens-min">
442 The minimum amount of tokens required to unhold processes
445 <key name="tokens-max">
450 <key name="priority-bias">
459 Contains the name of the vserver. When not given, the basename of the directory
460 will be assumed as this name.
465 The nice-level on which the vserver will be started.
468 <list name="capabilities">
470 Contains per line a capability. This file is used for the 2.4 kernel
471 only; for 2.6 use <optionref>bcapabilities</optionref>.
474 <scalar name="shell">
476 Contains the pathname of the shell which will be used by the "vserver
480 <list name="personality">
482 Used to set the personality of the vserver. First line in the file
483 is the personality-type followed by flags (one item per line). See
484 <filename>/usr/include/linux/personality.h</filename> for possible
490 Contains per line a flag. See <ulink
491 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/cflags-v13.c">lib/cflags-v13.c</ulink>
496 <element name="fakeinit">
498 The new process will believe it is process number 1. Useful to run a
499 real /sbin/init in a vserver. Warning: this flag should not be used
500 unless you know what you are doing. Often, it is better to use the
504 <element name="lock">
506 The new process is trapped and can't use chcontext anymore.
509 <element name="sched">
511 The new process and its children will share a common
514 <element name="nproc">
516 Limit the number of process in the vserver according to
517 ulimit setting. Normally, ulimit is a per user thing.
518 With this flag, it becomes a per vserver thing.
521 <element name="private">
523 No one can join this security context once created.
526 <element name="ulimit">
528 Apply the current ulimit to the whole context
534 <list name="nflags" since="0.30.212">
536 Contains a network flag per line. See <ulink
537 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/nflags-net.c">lib/nflags-net.c</ulink>
541 <scalar name="context">
543 Contains the context which shall be used for the vserver.
546 <data id="fstab" name="fstab">
548 The fstab file for the vserver. Entries in this file will be mounted
549 within the network context of the host. Use the
550 <optionref>fstab.remote</optionref> file when you want that the
551 mounting happens in the network context of the vserver. In most cases
552 the 'fstab' file should be used.
555 <data id="fstab.remote" name="fstab.remote">
557 The fstab file for the vserver. Entries in this file will be mounted
558 within the network context of the host; this means that mount will be
559 called as <command>chbind <options> mount ...</command>. See
560 <optionref>fstab</optionref> also.
564 <collection name="apps">
565 <collection name="init">
568 The initial-mtab which will be used for the vserver.
572 <scalar name="style">
574 Contains the init-style.
577 <enumeration value="sysv"/>
578 <enumeration value="plain"/>
579 <enumeration value="minit"/>
583 <scalar name="runlevel">
584 <description>The start runlevel.</description>
587 <scalar name="runlevel.start">
588 <description>The start runlevel.</description>
591 <scalar name="runlevel.stop">
592 <description>The stop runlevel.</description>
595 <scalar name="killseq">
597 Contains the 'signal [wait signal]*' sequence which is used to stop
602 <list name="cmd.start">
604 The command which is used to start the vserver. Each option must be on
609 <list name="cmd.start-sync">
611 The command which is used to wait on the vserver after it has been
612 started. Each option must be on a separate line. This file will be
613 ignored when the <optionref>sync</optionref> flag does not exist and the
614 '--sync' option was not used.
618 <list name="cmd.stop">
620 The command which is used to stop the vserver. Each option must be on
625 <list name="cmd.stop-sync">
627 The command which is used to wait on the vserver after it has been
628 stopped. Each option must be on a separate line. This file will be
629 ignored when the <optionref>sync</optionref> flag does not exist and the
630 '--sync' option was not used.
634 <list name="cmd.prepare">
636 The command which is used to setup the init-system (e.g. to set the
637 runlevel in the utmp-file). Each option must be on a separate line.
641 <boolean id="sync" name="sync">
643 If this file is not present, all 'cmd.*-sync files will be ignored.
649 A symlink to the TTY device where input/output will be redirected
650 from/to at startup via initscript.
656 This file is used to mark group of vservers which shall be started/stopped
657 together by the initscript. Content is a simple string like 'default'.
661 <list name="depends">
663 This file is used to configure vservers which must be running before
664 the current vserver can be started. At shutdown, the current vserver
665 will be stopped before its dependencies. Content of this file are
666 vserver ids (one name per line).
670 <hash name="environment" since="0.30.211">
672 The environment to set when starting the guest. Contains one VAR=VAL
678 <collection name="vshelper">
679 <scalar name="sync-timeout">
680 <default>30</default>
682 The timeout in seconds which is used when synchronising vserver
683 startup/shutdown with the vshelper. When not set, 30 seconds will be
688 <scalar name="action">
689 <default>restart</default>
691 The action which is going to be executed when a vshelper event
692 occurs. The default value is 'restart', but there can be defined own
693 methods by placing scripts into the
694 <optionref>vshelper-methods</optionref> directories. These scripts are
695 fed with the same arguments as the <tool>vshelper</tool> script.
699 <program name="event" type="symbolic">
701 When existing, these scripts will be executed *instead* of the default
702 handler defined in 'action'. Their name must match the event which caused
703 the execution of <tool>vshelper</tool>; e.g. 'restart' or 'poweroff'. See
704 the vs_reboot() function in the kernel for more details.
707 <parameter name="xid">
709 The xid of the context calling the vshelper
712 <parameter name="event">
720 <boolean name="disabled">
722 When existing, the vshelper functionality will be disabled for this
727 <boolean name="debug">
729 When existing, the vshelper execution will be traced for this vserver.
733 <boolean name="warning-disabled">
735 When existing, sanity checks for the vshelper functionality will be
742 <collection id="vshelper-methods" name="vshelper-methods">
743 <program name="handler" type="symbolic">
750 <collection name="vunify">
752 This directory contains configuration data required for vserver
756 <list name="exclude">
758 <p>Static list of files which are excluded for unification. This list
759 supports an rsync-like syntax: when a file is prefixed by '+', it is a
760 candidate for unification; when there is no prefix or a '-' or a '~' it
761 will be excluded. Shell-wildcards are allowed for the filenames.</p>
762 <p>When used with <tool>vcopy</tool>, the '~' prefix prevents copying
763 of the file entirely (e.g. for keyfiles). With this tool, the file will
764 be copied instead of hardlinked when the '-' prefix is used.</p>
768 <link name="refserver.X" type="symbolic">
770 These are symlinks to the configuration directory
771 (e.g. CONFDIR/vservers/<id>) of a refserver. There may be
772 multiple such symlinks but they must be prefixed by 'refserver.' and
773 will be processed in alphanumerical order.
777 <collection name="hash" since="0.30.205">
779 A directory which will be used as the storage place for the
780 <tool>vhashify</tool> command.
782 <link name="id" type="symbolic">
784 Points to a directory within the filesystems which are used for the
785 vservers. There must be not more than one of such a directory per
790 <scalar name="method" since="0.30.299">
791 <default>SHA1</default>
792 <description>The used hash method.</description>
796 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205">
798 When existing, information from packagemanagement will not be used to
799 create dynamic exclude-lists.
803 <boolean name="pgkmgmt-force" default="off" since="0.30.205">
805 When existing, information from packagemanagement will be used to
806 create dynamic exclude-lists. This option requires that (a known)
807 packagemanagement is configured for the vserver; else the requested
808 operation will fail. Most tools assume 'on' as the default value.
815 <collection name="scripts">
817 A directory for scripts. By default, when one of these scripts will be
818 executed, the execution of defaultscripts (within .../.defaults/scripts)
819 will be skipped. To execute them nevertheless, the $DONT_SKIP_DEFAULTS
820 environment variable must be set by one of the in-shellcontext scripts
821 (the non-executable ones).
824 <program name="initialize" since="0.30.211">
826 The scriptlet which will be executed before the root filesystem is mounted and
827 the configuration has been loaded. Before executing the script, the
828 configuration directory will be made the working directory.
831 <parameter name="action">
833 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
836 <parameter name="vserver-name">
838 The name of the current vserver.
843 <collection name="initialize.d" since="0.30.211">
845 Repository of initialize like scripts. Before executing the script,
846 the configuration directory will be made the working directory.
848 <program name="script" type="symbolic">
849 <description>See initialize.</description>
851 <parameter name="action">
853 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
856 <parameter name="vserver-name">
858 The name of the current vserver.
865 <program name="prepre-start">
867 The scriptlet which will be executed before the network-interfaces are
868 enabled and the directories are mounted. Before executing the script,
869 the configuration directory will be made the working directory.
872 <parameter name="action">
874 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
877 <parameter name="vserver-name">
879 The name of the current vserver.
884 <collection name="prepre-start.d">
886 Repository of prepre-start like scripts. Before executing the script,
887 the configuration directory will be made the working directory.
889 <program name="script" type="symbolic">
890 <description>See prepre-start.</description>
892 <parameter name="action">
894 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
897 <parameter name="vserver-name">
899 The name of the current vserver.
906 <program name="pre-start">
908 The scriptlet which will be executed after network-interfaces were
909 enabled and the directories mounted, but before the vserver itself has
910 been started. Before executing the script, the vserver root directory
911 will be made the working directory.
914 <parameter name="action">
916 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
919 <parameter name="vserver-name">
921 The name of the current vserver.
926 <collection name="pre-start.d">
928 Repository of pre-start like scripts. Before executing these scripts,
929 the vserver root directory will be made the working directory.
931 <program name="script" type="symbolic">
932 <description>See pre-start.</description>
934 <parameter name="action">
936 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
939 <parameter name="vserver-name">
941 The name of the current vserver.
949 <program name="post-start">
951 The scriptlet which will be executed after the vserver has been
952 started. Before executing the script, the vserver root directory
953 will be made the working directory.
956 <parameter name="action">
958 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
961 <parameter name="vserver-name">
963 The name of the current vserver.
968 <collection name="post-start.d">
970 Repository of post-start like scripts. Before executing these scripts,
971 the vserver root directory will be made the working directory.
973 <program name="script" type="symbolic">
974 <description>See post-start.</description>
976 <parameter name="action">
978 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
981 <parameter name="vserver-name">
983 The name of the current vserver.
991 <program name="pre-stop">
993 The scriptlet which will be executed before the vserver will be
994 stopped. Before executing the script, the vserver root directory
995 will be made the working directory.
998 <parameter name="action">
1000 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1003 <parameter name="vserver-name">
1005 The name of the current vserver.
1010 <collection name="pre-stop.d">
1012 Repository of pre-stop like scripts. Before executing the script, the
1013 vserver root directory will be made the working directory.
1015 <program name="script" type="symbolic">
1016 <description>See pre-stop.</description>
1018 <parameter name="action">
1020 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1023 <parameter name="vserver-name">
1025 The name of the current vserver.
1032 <program name="post-stop">
1034 The scriptlet which will be executed after the vserver has been
1035 stopped, but before the directories will be umounted and the the
1036 interfaces disabled. Before executing the script, the vserver root
1037 directory will be made the working directory.
1040 <parameter name="action">
1042 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1045 <parameter name="vserver-name">
1047 The name of the current vserver.
1052 <collection name="post-stop.d">
1054 Repository of post-stop like scripts. Before executing the script, the
1055 vserver root directory will be made the working directory.
1057 <program name="script" type="symbolic">
1058 <description>See post-stop.</description>
1060 <parameter name="action">
1062 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1065 <parameter name="vserver-name">
1067 The name of the current vserver.
1074 <program name="postpost-stop">
1076 The scriptlet which will be executed after the vserver has been stopped
1077 completely. Before executing the script, the vserver root directory
1078 will be made the working directory.
1081 <parameter name="action">
1083 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1086 <parameter name="vserver-name">
1088 The name of the current vserver.
1093 <collection name="postpost-stop.d">
1095 Repository of postpost-stop like scripts. Before executing the script,
1096 the vserver root directory will be made the working directory.
1098 <program name="script" type="symbolic">
1099 <description>See postpost-stop.</description>
1101 <parameter name="action">
1103 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1106 <parameter name="vserver-name">
1108 The name of the current vserver.
1116 <collection name="interfaces">
1117 <scalar name="bcast">
1118 <description>The default broadcast address.</description>
1121 <description>The default network device.</description>
1123 <scalar name="prefix">
1124 <description>The default network prefix-length.</description>
1126 <scalar name="mask">
1127 <description>The default network mask.</description>
1129 <scalar name="scope">
1130 <description>The default scope of the network interfaces.</description>
1132 <boolean id="local-vlandev" name="vlandev" since="0.30.211">
1134 When this file exists, the steps which setup and destroy a VLAN
1135 interface will be executed for all interfaces of this vserver.
1138 <boolean id="local-novlandev" name="novlandev">
1140 When this file exists, the steps which setup and destroy a VLAN
1141 interface will be skipped. This overrides the global
1142 <optionref ref="global-vlandev">vlandev</optionref> setting for
1147 <collection name="iface" type="symbolic">
1149 'iface' is an arbitrary name for the interface; the value itself is
1150 not important but may be interesting regarding interface-creation and
1151 usage with <tool>chbind</tool>. Both happens in alphabetical order and
1152 numbers like '00' are good names for these directories.
1155 <boolean name="disabled">
1156 <description>When this file exists, this interface will be ignored.</description>
1160 <description>The ip which will be assigned to this interface.</description>
1162 <scalar name="bcast">
1163 <description>The broadcast address.</description>
1166 <description>The network device.</description>
1168 <scalar name="prefix">
1169 <description>The network prefix-length.</description>
1171 <scalar name="mask">
1172 <description>The network mask.</description>
1174 <scalar name="scope">
1175 <description>The scope of the network interface.</description>
1177 <scalar name="name">
1179 When this file exists, the interface will be named with the text in
1180 this file. Without such an entry, the IP will not be shown by
1181 <tool>ifconfig</tool> but by <command>ip addr ls</command> only. Such
1182 a labeled interface is known as an "alias" also (e.g. 'eth0:foo').
1185 <boolean name="nodev">
1187 When this file exists, the interface will be assumed to exist
1188 already. This can be used to assign primary interfaces which are
1189 created by the host or another vserver.
1192 <boolean name="novlandev">
1194 When this file exists, the steps which setup and destroy a VLAN
1195 interface will be skipped. This will override the global
1196 <optionref ref="global-vlandev">vlandev</optionref> and the per-guest
1197 <optionref ref="local-vlandev">vlandev</optionref>.
1200 <boolean name="vlandev" since="0.30.211">
1202 When this file exists, the steps which setup and destroy a VLAN
1203 interface will be executed.
1209 <collection name="ulimits">
1211 A directory with ulimits. Possible resources are cpu, data, fsize,
1212 locks, memlock, nofile, nproc, rss and/or stack.
1214 <scalar name="resource" type="symbolic">
1216 A file which contains the hard- and soft-limit of the given resource
1217 in the first line. The special keyword 'inf' is recognized.
1220 <scalar name="resource.hard" type="symbolic">
1222 A file which contains the hard-limit of the given resource in the first
1223 line. The special keyword 'inf' is recognized.
1226 <scalar name="resource.soft" type="symbolic">
1228 A file which contains the soft-limit of the given resource in the first
1229 line. The special keyword 'inf' is recognized.
1234 <collection name="rlimits">
1236 A directory with resource limits. Possible resources are cpu, fsize,
1237 data, stack, core, rss, nproc, nofile, memlock, as, locks, msgqueue,
1238 nsock, openfd, anon, shmem, semary, nsems and dentry. This
1239 configuration will be honored for kernel 2.6 only.
1241 <scalar name="resource" type="symbolic">
1243 A file which contains the hard- and soft-limit of the given resource
1244 in the first line. The special keyword 'inf' is recognized.
1247 <scalar name="resource.hard" type="symbolic">
1249 A file which contains the hard-limit of the given resource in the first
1250 line. The special keyword 'inf' is recognized.
1253 <scalar name="resource.soft" type="symbolic">
1255 A file which contains the soft-limit of the given resource in the first
1256 line. The special keyword 'inf' is recognized.
1259 <scalar name="resource.min" type="symbolic">
1261 A file which contains the guaranteed minimum of the given resource in
1262 the first line. The special keyword 'inf' is recognized.
1267 <collection name="uts">
1268 <scalar name="context">
1270 The context-name of the vserver. This file is listed for completeness
1271 only; the 'context' name is used and set internally by the util-vserver
1272 tools and can *not* be modified.
1275 <scalar name="sysname">
1276 <description>The sysname of the vserver</description>
1278 <scalar name="nodename">
1279 <description>The node-/hostname of the vserver</description>
1281 <scalar name="release">
1282 <description>The OS-release of the vserver</description>
1284 <scalar name="version">
1285 <description>The OS-version of the vserver</description>
1287 <scalar name="machine">
1288 <description>The machine-type of the vserver</description>
1290 <scalar name="domainname">
1291 <description>The NIS domainname of the vserver</description>
1295 <collection name="dlimits" since="0.30.210">
1296 <collection name="dlimit" type="symbolic">
1297 <scalar name="directory">
1298 <description>The directory to which the limit should be applied</description>
1300 <scalar name="inodes_total">
1301 <description>The amount of inodes this vserver should be limited to</description>
1303 <scalar name="space_total">
1304 <description>The amount of space this vserver should be limited to (measured in blocks of 1024 bytes)</description>
1306 <scalar name="reserved">
1307 <description>How much space (percentage-wise) should be reserved for the root user</description>
1312 <collection name="cpuset" since="0.30.211">
1313 <scalar name="name">
1314 <description>The name of the cpuset for this vserver</description>
1316 <scalar name="cpus">
1317 <description>The list of CPUs in this cpuset</description>
1319 <scalar name="mems">
1320 <description>The list of Memory Nodes in this cpuset</description>
1322 <scalar name="cpu_exclusive">
1323 <description>Is the CPU assignment exclusive?</description>
1325 <scalar name="mems_exclusive">
1326 <description>Is the memory node assignment exclusive?</description>
1328 <scalar name="nocreate">
1329 <description>When this file exists, the cpuset will be assumed to exist already</description>
1333 <collection id="sched" name="sched" since="0.30.212">
1334 <scalar id="global-tokens" name="tokens">
1335 <description>The initial amount of tokens to put in the bucket</description>
1337 <scalar id="global-tokens-min" name="tokens-min">
1338 <description>The minimum amount of tokens required to unhold the context</description>
1340 <scalar id="global-tokens-max" name="tokens-max">
1341 <description>The bucket's size</description>
1343 <scalar id="global-fill-rate" name="fill-rate">
1344 <description>Amount of tokens to add each <optionref ref="global-interval">interval</optionref></description>
1346 <scalar id="global-interval" name="interval">
1347 <description>The interval between refills of the bucket</description>
1349 <scalar id="global-priority-bias" name="priority-bias">
1350 <description>Bias added to priorities calculated within the guest (result is clamped to -20/+19)</description>
1352 <scalar id="global-fill-rate2" name="fill-rate2">
1353 <description>Amount of tokens to add each <optionref ref="global-interval2">interval2</optionref> when advancing idle time</description>
1355 <scalar id="global-interval2" name="interval2">
1356 <description>The interval between refills of the bucket when advancing idle time</description>
1358 <boolean id="global-idle-time" name="idle-time">
1359 <description>When this file exists, advancing idle time is activated</description>
1361 <collection name="cpu-id" type="symbolic">
1362 <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>
1363 <scalar name="tokens">
1364 <description>The initial amount of tokens to put in the bucket</description>
1366 <scalar name="tokens-min">
1367 <description>The minimum amount of tokens required to unhold the context</description>
1369 <scalar name="tokens-max">
1370 <description>The bucket's size</description>
1372 <scalar name="fill-rate">
1373 <description>Amount of tokens to add each <optionref ref="local-interval">interval</optionref></description>
1375 <scalar id="local-interval" name="interval">
1376 <description>The interval between refills of the bucket</description>
1378 <scalar name="priority-bias">
1379 <description>Bias added to priorities calculated within the guest (result is clamped to -20/+19)</description>
1381 <scalar name="fill-rate2">
1382 <description>Amount of tokens to add each <optionref ref="local-interval2">interval2</optionref> when advancing idle time</description>
1384 <scalar id="local-interval2" name="interval2">
1385 <description>The interval between refills of the bucket when advancing idle time</description>
1387 <boolean name="idle-time">
1388 <description>When this file exists, advancing idle time is activated</description>
1390 <scalar id="cpu-id" name="cpu-id">
1391 <description>The CPU to apply these settings to</description>
1393 <scalar name="bucket-id">
1394 <description>The bucket to apply these settings to</description>