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-namespace-cleanup" name="namespace-cleanup">
42 Enable namespace cleanup globally. It can be overridden for a single vserver
43 by setting the <optionref ref="global-nonamespace-cleanup">nonamespace-cleanup</optionref> flag
50 Path of the vserver run reverse directory. This directory contains
51 symlinks named with XID numbers which point back to the configuration
52 directory of vservers. Under kernel 2.4 this is required for the XID
53 to VSERVER mapping; Under kernel 2.6 it is unused.
55 NOTE: this link exists in 0.30.202+ only; in previous versions it was
56 a vserver specific setting.
60 <collection name="apps">
61 <collection name="pkgmgmt">
63 <default>/vservers/.pkg</default>
65 <data name="apt.conf">
66 <description>The default apt.conf which is going to be used. It is overridden by
67 distribution specific configuration file.
72 <collection name="debootstrap">
73 <scalar name="mirror">
75 The Debian mirror to use with the <tool>debootstrap</tool> program
80 When the <tool>debootstrap</tool> package is not installed; fetch it
81 from this uri and install it at a temporary place.
86 <collection name="vshelper">
89 The file where output will be logged to when <tool>vshelper</tool>
90 is invoked from the kernel. This should point somewhere e.g. into
91 <directory>/var/log</directory>.
95 <collection name="vshelper-methods">
96 <program name="handler" type="symbolic">
103 <boolean name="disabled">
105 When existing, the vshelper functionality will be disabled for all
110 <boolean name="debug">
112 When existing, the vshelper execution will be traced.
116 <boolean name="warning-disabled">
118 When existing, sanity checks for the vshelper functionality will be
125 <collection name="vprocunhide">
128 A list of files which will be made visibly by vprocunhide. Wildcards are
129 allowed and anything ending in '/' will be processed recursively. When this file exists,
130 it overrides the defaults in SYSDEFAULTDIR/vprocunhide-files. The entries there must be
131 absolute filenames inclusive the leading '/proc'.
136 <collection name="init">
139 A symlink to the TTY device where input/output will be redirected from/to
140 at startup via initscript.
144 <list id="global-environment" name="environment">
146 The environment to set when starting guests. Contains one VAR=VAL
152 <collection name="vunify">
153 <list name="exclude">
154 <description>Static list of excluded files.</description>
157 <collection name="hash" since="0.30.205">
159 A directory which will be used as the storage place for the
160 <tool>vhashify</tool> command.
162 <link name="id" type="symbolic">
164 Points to a directory within the filesystems which are used for the
165 vservers. There must be not more than one of such a directory per
170 <scalar name="method" since="0.30.299">
171 <default>SHA1</default>
172 <description>The used hash method.</description>
176 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205">
178 When existing, information from packagemanagement will not be used to
179 create dynamic exclude-lists.
183 <boolean name="pgkmgmt-force" default="off" since="0.30.205">
185 When existing, information from packagemanagement will be used to
186 create dynamic exclude-lists. This option requires that (a known)
187 packagemanagement is configured for the vserver; else the requested
188 operation will fail. Most tools assume 'on' as the default value.
196 <collection name=".distributions" use="optional">
197 <collection name="dist" type="symbolic">
199 <description></description>
201 <collection name="yum">
203 The default, yum-related content of the <directory>/etc</directory>
206 <scalar name="yum.conf">
208 The master yum configuration file. It supports the @YUMETCDIR@,
209 @YUMCACHEDIR@ and @YUMLOGDIR@ placeholder which will be replaced at
210 <command>vserver ... build</command> time.
214 <collection name="yum.repos.d">
215 <description>A directory with yum repositories.</description>
217 <data name="apt.conf">
219 The default apt.conf which is going to be used. It overrides the
220 apt.conf from CONFDIR/.defaults/apps/pkgmgmt.
223 <program name="initpre">
225 Script which will be executed before packages will be installed.
228 <parameter name="confdir">
230 The configuration directory of the vserver which is going to be set up.
233 <parameter name="vserver">
235 The pathname of the vserver binary.
240 <program name="initpost">
242 Script which will be executed after packages are installed.
245 <parameter name="confdir">
247 The configuration directory of the vserver which is going to be set up.
250 <parameter name="vserver">
252 The pathname of the vserver binary.
258 <collection name="pkgs">
260 Contains files with packagenames.
264 File which contains the name of packages. On top of file the special
265 keywords '--reinstall' and '--can-fail' are possible.
270 <collection name="pubkeys">
272 Directory with GPG pubkeys which are used to sign the packages of this
277 <collection name="apt">
279 Default content of the <directory>/etc/apt/</directory> directory.
283 <collection name="rpm">
285 Default content of the <directory>/etc/rpm</directory> directory.
291 Directory which overrides <directory>/usr/lib/rpm</directory>.
294 <link name="execdir">
296 Directory with all executables and libraries which are required for
303 <!-- Vserver configuration -->
304 <collection name="vserver-name" type="symbolic">
306 The configuration directory for the vserver vserver-name.
310 <default>../.defaults/cachebase/VSERVERNAME</default>
312 Path of the storage area for cached information about this vserver.
317 <default>../.defaults/vdirbase/VSERVERNAME</default>
319 Path of the vserver root directory
325 Points to a file which will contain the XID of the running vserver. When
326 the vserver is stopped, this can be a dangling symlink.
330 <list id="bcapabilities" name="bcapabilities">
332 [experimental; name is subject of possible change] Contains the system capabilities. See
333 <ulink url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/bcaps-v13.c?rev=HEAD">lib/bcaps-v13.c</ulink>
337 <list name="ccapabilities">
339 [experimental; name is subject of possible change] Contains the
340 context capabilities. See <ulink
341 url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/ccaps-v13.c?rev=HEAD">lib/ccaps-v13.c</ulink>
346 <boolean id="global-namespace" name="namespace">
348 Overrides the global <optionref ref="global-nonamespace">nonamespace</optionref> flag and enables
349 namespace usage for the current vserver.
353 <boolean name="nonamespace">
355 Disables namespace usage for the current vserver.
357 In this mode the <directory>/vservers</directory> directory must have
358 the 'barrier' attribute. Else, common chroot(2) exploits are possible.
362 <boolean id="global-nonamespace-cleanup" name="nonamespace-cleanup">
364 Overrides the global <optionref ref="global-namespace-cleanup">namespace-cleanup</optionref> flag and disables
365 namespace cleanup for the current vserver.
369 <boolean name="namespace-cleanup">
371 Enable namespace cleanup for the current vserver.
375 <hash name="schedule">
377 [experimental; name is subject of possible change] Contains the
378 scheduler parameters, one per line.
380 The Hard CPU limit uses a mechanism called a Token Bucket. the
381 concept is simple: you have a bucket of a certain size which is
382 filled with a specified amount R of tokens each interval T until the
383 maximum is reached (excess tokens are spilled). At each timer tick,
384 a running process consumes one token from the bucket, unless the
385 bucket is empty. If the bucket is empty the process is put in the
386 hold queue. When the bucket has been refilled to at least M tokens,
387 all on hold processes are rescheduled.
389 See the <ulink url="http://linux-vserver.org/Scheduler+Parameters">Linux
390 VServer Wiki</ulink> for more information about this file.
393 <key id="fill_rate" name="fill-rate">
395 Amount of tokens append to the bucket each interval.
398 <key name="interval">
400 The intervall between refills of amount <optionref>fill_rate</optionref>. This
401 value is express in ticks.
406 Initial bucket contents.
409 <key name="tokens-min">
411 The minimum amount of tokens required to unhold processes
414 <key name="tokens-max">
419 <key name="priority-bias">
428 Contains the name of the vserver. When not given, the basename of the directory
429 will be assumed as this name.
434 The nice-level on which the vserver will be started.
437 <list name="capabilities">
439 Contains per line a capability. This file is used for the 2.4 kernel
440 only; for 2.6 use <optionref>bcapabilities</optionref>.
443 <scalar name="shell">
445 Contains the pathname of the shell which will be used by the "vserver
449 <list name="personality">
451 Used to set the personality of the vserver. First line in the file
452 is the personality-type followed by flags (one item per line). See
453 <filename>/usr/include/linux/personality.h</filename> for possible
459 Contains per line a flag. See <ulink
460 url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/cflags-v13.c?rev=HEAD">lib/cflags-v13.c</ulink>
465 <element name="fakeinit">
467 The new process will believe it is process number 1. Useful to run a
468 real /sbin/init in a vserver. Warning: this flag should not be used
469 unless you know what you are doing. Often, it is better to use the
473 <element name="lock">
475 The new process is trapped and can't use chcontext anymore.
478 <element name="sched">
480 The new process and its children will share a common
483 <element name="nproc">
485 Limit the number of process in the vserver according to
486 ulimit setting. Normally, ulimit is a per user thing.
487 With this flag, it becomes a per vserver thing.
490 <element name="private">
492 No one can join this security context once created.
495 <element name="ulimit">
497 Apply the current ulimit to the whole context
503 <scalar name="context">
505 Contains the context which shall be used for the vserver.
508 <data id="fstab" name="fstab">
510 The fstab file for the vserver. Entries in this file will be mounted
511 within the network context of the host. Use the
512 <optionref>fstab.remote</optionref> file when you want that the
513 mounting happens in the network context of the vserver. In most cases
514 the 'fstab' file should be used.
517 <data id="fstab.remote" name="fstab.remote">
519 The fstab file for the vserver. Entries in this file will be mounted
520 within the network context of the host; this means that mount will be
521 called as <command>chbind <options> mount ...</command>. See
522 <optionref>fstab</optionref> also.
526 <collection name="apps">
527 <collection name="init">
530 The initial-mtab which will be used for the vserver.
534 <scalar name="style">
536 Contains the init-style.
539 <enumeration value="sysv"/>
540 <enumeration value="plain"/>
541 <enumeration value="minit"/>
542 <enumeration value="gento"/>
546 <scalar name="runlevel">
547 <description>The start runlevel.</description>
550 <scalar name="runlevel.start">
551 <description>The start runlevel.</description>
554 <scalar name="runlevel.stop">
555 <description>The stop runlevel.</description>
558 <scalar name="killseq">
560 Contains the 'signal [wait signal]*' sequence which is used to stop
565 <list name="cmd.start">
567 The command which is used to start the vserver. Each option must be on
572 <list name="cmd.start-sync">
574 The command which is used to wait on the vserver after it has been
575 started. Each option must be on a separate line. This file will be
576 ignored when the <optionref>sync</optionref> flag does not exist and the
577 '--sync' option was not used.
581 <list name="cmd.stop">
583 The command which is used to stop the vserver. Each option must be on
588 <list name="cmd.stop-sync">
590 The command which is used to wait on the vserver after it has been
591 stopped. Each option must be on a separate line. This file will be
592 ignored when the <optionref>sync</optionref> flag does not exist and the
593 '--sync' option was not used.
597 <list name="cmd.prepare">
599 The command which is used to setup the init-system (e.g. to set the
600 runlevel in the utmp-file). Each option must be on a separate line.
604 <boolean id="sync" name="sync">
606 If this file is not present, all 'cmd.*-sync files will be ignored.
612 A symlink to the TTY device where input/output will be redirected
613 from/to at startup via initscript.
619 This file is used to mark group of vservers which shall be started/stopped
620 together by the initscript. Content is a simple string like 'default'.
624 <list name="depends">
626 This file is used to configure vservers which must be running before
627 the current vserver can be started. At shutdown, the current vserver
628 will be stopped before its dependencies. Content of this file are
629 vserver ids (one name per line).
633 <list name="environment">
635 The environment to set when starting the guest. Contains one VAR=VAL
641 <collection name="vshelper">
642 <scalar name="sync-timeout">
643 <default>30</default>
645 The timeout in seconds which is used when synchronising vserver
646 startup/shutdown with the vshelper. When no set, 30 seconds will be
651 <scalar name="action">
652 <default>restart</default>
654 The action which is going to be executed when a vshelper event
655 occurs. The default value is 'restart', but there can be defined own
656 methods by placing scripts into the
657 <optionref>vshelper-methods</optionref> directories. These scripts are
658 fed with the same arguments as the <tool>vshelper</tool> script.
662 <program name="event" type="symbolic">
664 When existing, these scripts will be executed *instead* of the default
665 handler defined in 'action'. Their name must match the event which caused
666 the execution of <tool>vshelper</tool>; e.g. 'restart' or 'poweroff'. See
667 the vs_reboot() function in the kernel for more details.
670 <parameter name="xid">
672 The xid of the context calling the vshelper
675 <parameter name="event">
683 <boolean name="disabled">
685 When existing, the vshelper functionality will be disabled for this
690 <boolean name="debug">
692 When existing, the vshelper execution will be traced for this vserver.
696 <boolean name="warning-disabled">
698 When existing, sanity checks for the vshelper functionality will be
705 <collection id="vshelper-methods" name="vshelper-methods">
706 <program name="handler" type="symbolic">
713 <collection name="vunify">
715 This directory contains configuration data required for vserver
719 <list name="exclude">
721 <p>Static list of files which are excluded for unification. This list
722 supports an rsync-like syntax: when a file is prefixed by '+', it is a
723 candidate for unification; when there is no prefix or a '-' or a '~' it
724 will be excluded. Shell-wildcards are allowed for the filenames.</p>
725 <p>When used with <tool>vcopy</tool>, the '~' prefix prevents copying
726 of the file entirely (e.g. for keyfiles). With this tool, the file will
727 be copied instead of hardlinked when the '-' prefix is used.</p>
731 <link name="refserver.X" type="symbolic">
733 These are symlinks to the configuration directory
734 (e.g. CONFDIR/vservers/<id>) of a refserver. There may be
735 multiple such symlinks but they must be prefixed by 'refserver.' and
736 will be processed in alphanumerical order.
740 <collection name="hash" since="0.30.205">
742 A directory which will be used as the storage place for the
743 <tool>vhashify</tool> command.
745 <link name="id" type="symbolic">
747 Points to a directory within the filesystems which are used for the
748 vservers. There must be not more than one of such a directory per
753 <scalar name="method" since="0.30.299">
754 <default>SHA1</default>
755 <description>The used hash method.</description>
759 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205">
761 When existing, information from packagemanagement will not be used to
762 create dynamic exclude-lists.
766 <boolean name="pgkmgmt-force" default="off" since="0.30.205">
768 When existing, information from packagemanagement will be used to
769 create dynamic exclude-lists. This option requires that (a known)
770 packagemanagement is configured for the vserver; else the requested
771 operation will fail. Most tools assume 'on' as the default value.
778 <collection name="scripts">
780 A directory for scripts. By default, when one of these scripts will be
781 executed, the execution of defaultscripts (within .../.defaults/scripts)
782 will be skipped. To execute them nevertheless, the $DONT_SKIP_DEFAULTS
783 environment variable must be set by one of the in-shellcontext scripts
784 (the non-executable ones).
787 <program name="initialize">
789 The scriptlet which will be executed before the root filesystem is mounted and
790 the configuration has been loaded. Before executing the script, the
791 configuration directory will be made the working directory.
794 <parameter name="vserver-dir">
796 The configuration directory of the current vserver.
799 <parameter name="vserver-name">
801 The name of the current vserver.
804 <parameter name="action">
806 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
811 <collection name="initialize.d">
813 Repository of initialize like scripts. Before executing the script,
814 the configuration directory will be made the working directory.
816 <program name="script" type="symbolic">
817 <description>See initialize.</description>
819 <parameter name="vserver-dir">
821 The configuration directory of the current vserver.
824 <parameter name="vserver-name">
826 The name of the current vserver.
829 <parameter name="action">
831 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
838 <program name="prepre-start">
840 The scriptlet which will be executed before the network-interfaces are
841 enabled and the directories are mounted. Before executing the script,
842 the configuration directory will be made the working directory.
845 <parameter name="vserver-dir">
847 The configuration directory of the current vserver.
850 <parameter name="vserver-name">
852 The name of the current vserver.
855 <parameter name="action">
857 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
862 <collection name="prepre-start.d">
864 Repository of prepre-start like scripts. Before executing the script,
865 the configuration directory will be made the working directory.
867 <program name="script" type="symbolic">
868 <description>See prepre-start.</description>
870 <parameter name="vserver-dir">
872 The configuration directory of the current vserver.
875 <parameter name="vserver-name">
877 The name of the current vserver.
880 <parameter name="action">
882 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
889 <program name="pre-start">
891 The scriptlet which will be executed after network-interfaces were
892 enabled and the directories mounted, but before the vserver itself has
893 been started. Before executing the script, the vserver root directory
894 will be made the working directory.
897 <parameter name="vserver-dir">
899 The configuration directory of the current vserver.
902 <parameter name="vserver-name">
904 The name of the current vserver.
907 <parameter name="action">
909 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
914 <collection name="pre-start.d">
916 Repository of pre-start like scripts. Before executing these scripts,
917 the vserver root directory will be made the working directory.
919 <program name="script" type="symbolic">
920 <description>See pre-start.</description>
922 <parameter name="vserver-dir">
924 The configuration directory of the current vserver.
927 <parameter name="vserver-name">
928 <description>The name of the current vserver.</description>
930 <parameter name="action">
932 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
940 <program name="post-start">
942 The scriptlet which will be executed after the vserver has been
943 started. Before executing the script, the vserver root directory
944 will be made the working directory.
947 <parameter name="vserver-dir">
948 <description>The configuration directory of the current vserver.</description>
950 <parameter name="vserver-name">
951 <description>The name of the current vserver.</description>
953 <parameter name="action">
955 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
960 <collection name="post-start.d">
962 Repository of post-start like scripts. Before executing these scripts,
963 the vserver root directory will be made the working directory.
965 <program name="script" type="symbolic">
966 <description>See post-start.</description>
968 <parameter name="vserver-dir">
969 <description>The configuration directory of the current vserver.</description>
971 <parameter name="vserver-name">
972 <description>The name of the current vserver.</description>
974 <parameter name="action">
976 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
984 <program name="pre-stop">
986 The scriptlet which will be executed before the vserver will be
987 stopped. Before executing the script, the vserver root directory
988 will be made the working directory.
991 <parameter name="vserver-dir">
992 <description>The configuration directory of the current vserver.</description>
994 <parameter name="vserver-name">
995 <description>The name of the current vserver.</description>
997 <parameter name="action">
999 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1004 <collection name="pre-stop.d">
1006 Repository of pre-stop like scripts. Before executing the script, the
1007 vserver root directory will be made the working directory.
1009 <program name="script" type="symbolic">
1010 <description>See pre-stop.</description>
1012 <parameter name="vserver-dir">
1013 <description>The configuration directory of the current vserver.</description>
1015 <parameter name="vserver-name">
1016 <description>The name of the current vserver.</description>
1018 <parameter name="action">
1020 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1027 <program name="post-stop">
1029 The scriptlet which will be executed after the vserver has been
1030 stopped, but before the directories will be umounted and the the
1031 interfaces disabled. Before executing the script, the vserver root
1032 directory will be made the working directory.
1035 <parameter name="vserver-dir">
1036 <description>The configuration directory of the current vserver.</description>
1038 <parameter name="vserver-name">
1039 <description>The name of the current vserver.</description>
1041 <parameter name="action">
1043 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1048 <collection name="post-stop.d">
1050 Repository of post-stop like scripts. Before executing the script, the
1051 vserver root directory will be made the working directory.
1053 <program name="script" type="symbolic">
1054 <description>See post-stop.</description>
1056 <parameter name="vserver-dir">
1057 <description>The configuration directory of the current vserver.</description>
1059 <parameter name="vserver-name">
1060 <description>The name of the current vserver.</description>
1062 <parameter name="action">
1064 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1071 <program name="postpost-stop">
1073 The scriptlet which will be executed after the vserver has been stopped
1074 completely. Before executing the script, the vserver root directory
1075 will be made the working directory.
1078 <parameter name="vserver-dir">
1079 <description>The configuration directory of the current vserver.</description>
1081 <parameter name="vserver-name">
1082 <description>The name of the current vserver.</description>
1084 <parameter name="action">
1086 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1091 <collection name="postpost-stop.d">
1093 Repository of postpost-stop like scripts. Before executing the script,
1094 the vserver root directory will be made the working directory.
1096 <program name="script" type="symbolic">
1097 <description>See postpost-stop.</description>
1099 <parameter name="vserver-dir">
1100 <description>The configuration directory of the current vserver.</description>
1102 <parameter name="vserver-name">
1103 <description>The name of the current vserver.</description>
1105 <parameter name="action">
1107 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1115 <collection name="interfaces">
1116 <scalar name="bcast">
1117 <description>The default broadcast address.</description>
1120 <description>The default network device.</description>
1122 <scalar name="prefix">
1123 <description>The default network prefix-length.</description>
1125 <scalar name="mask">
1126 <description>The default network mask.</description>
1128 <scalar name="scope">
1129 <description>The default scope of the network interfaces.</description>
1132 <collection name="iface" type="symbolic">
1134 'iface' is an arbitrary name for the interface; the value itself is
1135 not important but may be interesting regarding interface-creation and
1136 usage with <tool>chbind</tool>. Both happens in alphabetical order and
1137 numbers like '00' are good names for these directories.
1140 <boolean name="disabled">
1141 <description>When this file exists, this interface will be ignored.</description>
1145 <description>The ip which will be assigned to this interface.</description>
1147 <scalar name="bcast">
1148 <description>The broadcast address.</description>
1151 <description>The network device.</description>
1153 <scalar name="prefix">
1154 <description>The network prefix-length.</description>
1156 <scalar name="mask">
1157 <description>The network mask.</description>
1159 <scalar name="scope">
1160 <description>The scope of the network interface.</description>
1162 <scalar name="name">
1164 When this file exists, the interface will be named with the text in
1165 this file. Without such an entry, the IP will not be shown by
1166 <tool>ifconfig</tool> but by <command>ip addr ls</command> only. Such
1167 a labeled interface is known as an "alias" also (e.g. 'eth0:foo').
1170 <boolean name="nodev">
1172 When this file exists, the interface will be assumed to exist
1173 already. This can be used to assign primary interfaces which are
1174 created by the host or another vserver.
1177 <boolean name="novlandev">
1179 When this file exists, the steps which setup and destroy a VLAN
1180 interface will be skipped. This flag should be set when a VLAN
1181 interface is used by multiple vservers or by the host.
1187 <collection name="ulimits">
1189 A directory with ulimits. Possible resources are cpu, data, fsize,
1190 locks, memlock, nofile, nproc, rss and/or stack. This configuration
1191 will be honored for kernel 2.4 only.
1193 <scalar name="resource" type="symbolic">
1195 A file which contains the hard- and soft-limit of the given resource
1196 in the first line. The special keyword 'inf' is recognized.
1199 <scalar name="resource.hard" type="symbolic">
1201 A file which contains the hard- of the given resource in the first
1202 line. The special keyword 'inf' is recognized.
1205 <scalar name="resource.soft" type="symbolic">
1207 A file which contains the soft- of the given resource in the first
1208 line. The special keyword 'inf' is recognized.
1213 <collection name="rlimits">
1215 A directory with resource limits. Possible resources are cpu, fsize,
1216 data, stack, core, rss, nproc, nofile, memlock, as and locks. This
1217 configuration will be honored for kernel 2.6 only.
1219 <scalar name="resource" type="symbolic">
1221 A file which contains the hard- and soft-limit of the given resource
1222 in the first line. The special keyword 'inf' is recognized.
1225 <scalar name="resource.hard" type="symbolic">
1227 A file which contains the hard- of the given resource in the first
1228 line. The special keyword 'inf' is recognized.
1231 <scalar name="resource.soft" type="symbolic">
1233 A file which contains the soft- of the given resource in the first
1234 line. The special keyword 'inf' is recognized.
1237 <scalar name="resource.min" type="symbolic">
1239 A file which contains the guaranted minimum of the given resource in
1240 the first line. The special keyword 'inf' is recognized.
1245 <collection name="uts">
1246 <scalar name="context">
1248 The context-name of the vserver. This file is listed for completeness
1249 only; the 'context' name is used and set internally by the util-vserver
1250 tools and can *not* be modified.
1253 <scalar name="sysname">
1254 <description>The sysname of the vserver</description>
1256 <scalar name="nodename">
1257 <description>The node-/hostname of the vserver</description>
1259 <scalar name="release">
1260 <description>The OS-release of the vserver</description>
1262 <scalar name="version">
1263 <description>The OS-version of the vserver</description>
1265 <scalar name="machine">
1266 <description>The machine-type of the vserver</description>
1268 <scalar name="domainname">
1269 <description>The NIS domainname of the vserver</description>
1273 <collection name="dlimits">
1274 <collection name="dlimit" type="symbolic">
1275 <scalar name="directory">
1276 <description>The directory to which the limit should be applied</description>
1278 <scalar name="inodes_total">
1279 <description>The amount of inodes this vserver should be limited to</description>
1281 <scalar name="space_total">
1282 <description>The amount of space this vserver should be limited to (measured in blocks of 1024 bytes)</description>
1284 <scalar name="reserved">
1285 <description>How much space (percentage-wise) should be reserved for the root user</description>
1290 <collection name="cpuset">
1291 <scalar name="name">
1292 <description>The name of the cpuset for this vserver</description>
1294 <scalar name="cpus">
1295 <description>The list of CPUs in this cpuset</description>
1297 <scalar name="mems">
1298 <description>The list of Memory Nodes in this cpuset</description>
1300 <scalar name="cpu_exclusive">
1301 <description>Is the CPU assignment exclusive?</description>
1303 <scalar name="mems_exclusive">
1304 <description>Is the memory node assignment exclusive?</description>
1306 <scalar name="nocreate">
1307 <description>When this file exists, the cpuset will be assumed to exist already</description>