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.
145 <collection name="vunify">
146 <list name="exclude">
147 <description>Static list of excluded files.</description>
150 <collection name="hash" since="0.30.205">
152 A directory which will be used as the storage place for the
153 <tool>vhashify</tool> command.
155 <link name="id" type="symbolic">
157 Points to a directory within the filesystems which are used for the
158 vservers. There must be not more than one of such a directory per
163 <scalar name="method" since="0.30.299">
164 <default>SHA1</default>
165 <description>The used hash method.</description>
169 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205">
171 When existing, information from packagemanagement will not be used to
172 create dynamic exclude-lists.
176 <boolean name="pgkmgmt-force" default="off" since="0.30.205">
178 When existing, information from packagemanagement will be used to
179 create dynamic exclude-lists. This option requires that (a known)
180 packagemanagement is configured for the vserver; else the requested
181 operation will fail. Most tools assume 'on' as the default value.
189 <collection name=".distributions" use="optional">
190 <collection name="dist" type="symbolic">
192 <description></description>
194 <collection name="yum">
196 The default, yum-related content of the <directory>/etc</directory>
199 <scalar name="yum.conf">
201 The master yum configuration file. It supports the @YUMETCDIR@,
202 @YUMCACHEDIR@ and @YUMLOGDIR@ placeholder which will be replaced at
203 <command>vserver ... build</command> time.
207 <collection name="yum.repos.d">
208 <description>A directory with yum repositories.</description>
210 <data name="apt.conf">
212 The default apt.conf which is going to be used. It overrides the
213 apt.conf from CONFDIR/.defaults/apps/pkgmgmt.
216 <program name="initpre">
218 Script which will be executed before packages will be installed.
221 <parameter name="confdir">
223 The configuration directory of the vserver which is going to be set up.
226 <parameter name="vserver">
228 The pathname of the vserver binary.
233 <program name="initpost">
235 Script which will be executed after packages are installed.
238 <parameter name="confdir">
240 The configuration directory of the vserver which is going to be set up.
243 <parameter name="vserver">
245 The pathname of the vserver binary.
251 <collection name="pkgs">
253 Contains files with packagenames.
257 File which contains the name of packages. On top of file the special
258 keywords '--reinstall' and '--can-fail' are possible.
263 <collection name="pubkeys">
265 Directory with GPG pubkeys which are used to sign the packages of this
270 <collection name="apt">
272 Default content of the <directory>/etc/apt/</directory> directory.
276 <collection name="rpm">
278 Default content of the <directory>/etc/rpm</directory> directory.
284 Directory which overrides <directory>/usr/lib/rpm</directory>.
287 <link name="execdir">
289 Directory with all executables and libraries which are required for
296 <!-- Vserver configuration -->
297 <collection name="vserver-name" type="symbolic">
299 The configuration directory for the vserver vserver-name.
303 <default>../.defaults/cachebase/VSERVERNAME</default>
305 Path of the storage area for cached information about this vserver.
310 <default>../.defaults/vdirbase/VSERVERNAME</default>
312 Path of the vserver root directory
318 Points to a file which will contain the XID of the running vserver. When
319 the vserver is stopped, this can be a dangling symlink.
323 <list id="bcapabilities" name="bcapabilities">
325 [experimental; name is subject of possible change] Contains the system capabilities. See
326 <ulink url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/bcaps-v13.c?rev=HEAD">lib/bcaps-v13.c</ulink>
330 <list name="ccapabilities">
332 [experimental; name is subject of possible change] Contains the
333 context capabilities. See <ulink
334 url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/ccaps-v13.c?rev=HEAD">lib/ccaps-v13.c</ulink>
339 <boolean id="global-namespace" name="namespace">
341 Overrides the global <optionref ref="global-nonamespace">nonamespace</optionref> flag and enables
342 namespace usage for the current vserver.
346 <boolean name="nonamespace">
348 Disables namespace usage for the current vserver.
350 In this mode the <directory>/vservers</directory> directory must have
351 the 'barrier' attribute. Else, common chroot(2) exploits are possible.
355 <boolean id="global-nonamespace-cleanup" name="nonamespace-cleanup">
357 Overrides the global <optionref ref="global-namespace-cleanup">namespace-cleanup</optionref> flag and disables
358 namespace cleanup for the current vserver.
362 <boolean name="namespace-cleanup">
364 Enable namespace cleanup for the current vserver.
368 <hash name="schedule">
370 [experimental; name is subject of possible change] Contains the
371 scheduler parameters, one per line.
373 The Hard CPU limit uses a mechanism called a Token Bucket. the
374 concept is simple: you have a bucket of a certain size which is
375 filled with a specified amount R of tokens each interval T until the
376 maximum is reached (excess tokens are spilled). At each timer tick,
377 a running process consumes one token from the bucket, unless the
378 bucket is empty. If the bucket is empty the process is put in the
379 hold queue. When the bucket has been refilled to at least M tokens,
380 all on hold processes are rescheduled.
382 See the <ulink url="http://linux-vserver.org/Scheduler+Parameters">Linux
383 VServer Wiki</ulink> for more information about this file.
386 <key id="fill_rate" name="fill-rate">
388 Amount of tokens append to the bucket each interval.
391 <key name="interval">
393 The intervall between refills of amount <optionref>fill_rate</optionref>. This
394 value is express in ticks.
399 Initial bucket contents.
402 <key name="tokens-min">
404 The minimum amount of tokens required to unhold processes
407 <key name="tokens-max">
412 <key name="priority-bias">
421 Contains the name of the vserver. When not given, the basename of the directory
422 will be assumed as this name.
427 The nice-level on which the vserver will be started.
430 <list name="capabilities">
432 Contains per line a capability. This file is used for the 2.4 kernel
433 only; for 2.6 use <optionref>bcapabilities</optionref>.
436 <scalar name="shell">
438 Contains the pathname of the shell which will be used by the "vserver
442 <list name="personality">
444 Used to set the personality of the vserver. First line in the file
445 is the personality-type followed by flags (one item per line). See
446 <filename>/usr/include/linux/personality.h</filename> for possible
452 Contains per line a flag. See <ulink
453 url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/cflags-v13.c?rev=HEAD">lib/cflags-v13.c</ulink>
458 <element name="fakeinit">
460 The new process will believe it is process number 1. Useful to run a
461 real /sbin/init in a vserver. Warning: this flag should not be used
462 unless you know what you are doing. Often, it is better to use the
466 <element name="lock">
468 The new process is trapped and can't use chcontext anymore.
471 <element name="sched">
473 The new process and its children will share a common
476 <element name="nproc">
478 Limit the number of process in the vserver according to
479 ulimit setting. Normally, ulimit is a per user thing.
480 With this flag, it becomes a per vserver thing.
483 <element name="private">
485 No one can join this security context once created.
488 <element name="ulimit">
490 Apply the current ulimit to the whole context
496 <scalar name="context">
498 Contains the context which shall be used for the vserver.
501 <data id="fstab" name="fstab">
503 The fstab file for the vserver. Entries in this file will be mounted
504 within the network context of the host. Use the
505 <optionref>fstab.remote</optionref> file when you want that the
506 mounting happens in the network context of the vserver. In most cases
507 the 'fstab' file should be used.
510 <data id="fstab.remote" name="fstab.remote">
512 The fstab file for the vserver. Entries in this file will be mounted
513 within the network context of the host; this means that mount will be
514 called as <command>chbind <options> mount ...</command>. See
515 <optionref>fstab</optionref> also.
519 <collection name="apps">
520 <collection name="init">
523 The initial-mtab which will be used for the vserver.
527 <scalar name="style">
529 Contains the init-style.
532 <enumeration value="sysv"/>
533 <enumeration value="plain"/>
534 <enumeration value="minit"/>
535 <enumeration value="gento"/>
539 <scalar name="runlevel">
540 <description>The start runlevel.</description>
543 <scalar name="runlevel.start">
544 <description>The start runlevel.</description>
547 <scalar name="runlevel.stop">
548 <description>The stop runlevel.</description>
551 <scalar name="killseq">
553 Contains the 'signal [wait signal]*' sequence which is used to stop
558 <list name="cmd.start">
560 The command which is used to start the vserver. Each option must be on
565 <list name="cmd.start-sync">
567 The command which is used to wait on the vserver after it has been
568 started. Each option must be on a separate line. This file will be
569 ignored when the <optionref>sync</optionref> flag does not exist and the
570 '--sync' option was not used.
574 <list name="cmd.stop">
576 The command which is used to stop the vserver. Each option must be on
581 <list name="cmd.stop-sync">
583 The command which is used to wait on the vserver after it has been
584 stopped. Each option must be on a separate line. This file will be
585 ignored when the <optionref>sync</optionref> flag does not exist and the
586 '--sync' option was not used.
590 <list name="cmd.prepare">
592 The command which is used to setup the init-system (e.g. to set the
593 runlevel in the utmp-file). Each option must be on a separate line.
597 <boolean id="sync" name="sync">
599 If this file is not present, all 'cmd.*-sync files will be ignored.
605 A symlink to the TTY device where input/output will be redirected
606 from/to at startup via initscript.
612 This file is used to mark group of vservers which shall be started/stopped
613 together by the initscript. Content is a simple string like 'default'.
617 <list name="depends">
619 This file is used to configure vservers which must be running before
620 the current vserver can be started. At shutdown, the current vserver
621 will be stopped before its dependencies. Content of this file are
622 vserver ids (one name per line).
627 <collection name="vshelper">
628 <scalar name="sync-timeout">
629 <default>30</default>
631 The timeout in seconds which is used when synchronising vserver
632 startup/shutdown with the vshelper. When no set, 30 seconds will be
637 <scalar name="action">
638 <default>restart</default>
640 The action which is going to be executed when a vshelper event
641 occurs. The default value is 'restart', but there can be defined own
642 methods by placing scripts into the
643 <optionref>vshelper-methods</optionref> directories. These scripts are
644 fed with the same arguments as the <tool>vshelper</tool> script.
648 <program name="event" type="symbolic">
650 When existing, these scripts will be executed *instead* of the default
651 handler defined in 'action'. Their name must match the event which caused
652 the execution of <tool>vshelper</tool>; e.g. 'restart' or 'poweroff'. See
653 the vs_reboot() function in the kernel for more details.
656 <parameter name="xid">
658 The xid of the context calling the vshelper
661 <parameter name="event">
669 <boolean name="disabled">
671 When existing, the vshelper functionality will be disabled for this
676 <boolean name="debug">
678 When existing, the vshelper execution will be traced for this vserver.
682 <boolean name="warning-disabled">
684 When existing, sanity checks for the vshelper functionality will be
691 <collection id="vshelper-methods" name="vshelper-methods">
692 <program name="handler" type="symbolic">
699 <collection name="vunify">
701 This directory contains configuration data required for vserver
705 <list name="exclude">
707 <p>Static list of files which are excluded for unification. This list
708 supports an rsync-like syntax: when a file is prefixed by '+', it is a
709 candidate for unification; when there is no prefix or a '-' or a '~' it
710 will be excluded. Shell-wildcards are allowed for the filenames.</p>
711 <p>When used with <tool>vcopy</tool>, the '~' prefix prevents copying
712 of the file entirely (e.g. for keyfiles). With this tool, the file will
713 be copied instead of hardlinked when the '-' prefix is used.</p>
717 <link name="refserver.X" type="symbolic">
719 These are symlinks to the configuration directory
720 (e.g. CONFDIR/vservers/<id>) of a refserver. There may be
721 multiple such symlinks but they must be prefixed by 'refserver.' and
722 will be processed in alphanumerical order.
726 <collection name="hash" since="0.30.205">
728 A directory which will be used as the storage place for the
729 <tool>vhashify</tool> command.
731 <link name="id" type="symbolic">
733 Points to a directory within the filesystems which are used for the
734 vservers. There must be not more than one of such a directory per
739 <scalar name="method" since="0.30.299">
740 <default>SHA1</default>
741 <description>The used hash method.</description>
745 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205">
747 When existing, information from packagemanagement will not be used to
748 create dynamic exclude-lists.
752 <boolean name="pgkmgmt-force" default="off" since="0.30.205">
754 When existing, information from packagemanagement will be used to
755 create dynamic exclude-lists. This option requires that (a known)
756 packagemanagement is configured for the vserver; else the requested
757 operation will fail. Most tools assume 'on' as the default value.
764 <collection name="scripts">
766 A directory for scripts. By default, when one of these scripts will be
767 executed, the execution of defaultscripts (within .../.defaults/scripts)
768 will be skipped. To execute them nevertheless, the $DONT_SKIP_DEFAULTS
769 environment variable must be set by one of the in-shellcontext scripts
770 (the non-executable ones).
773 <program name="prepre-start">
775 The scriptlet which will be executed before the network-interfaces are
776 enabled and the directories are mounted. Before executing the script,
777 the configuration directory will be made the working directory.
780 <parameter name="vserver-dir">
782 The configuration directory of the current vserver.
785 <parameter name="vserver-name">
787 The name of the current vserver.
790 <parameter name="action">
792 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
797 <collection name="prepre-start.d">
799 Repository of prepre-start like scripts. Before executing the script,
800 the configuration directory will be made the working directory.
802 <program name="script" type="symbolic">
803 <description>See prepre-start.</description>
805 <parameter name="vserver-dir">
807 The configuration directory of the current vserver.
810 <parameter name="vserver-name">
812 The name of the current vserver.
815 <parameter name="action">
817 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
824 <program name="pre-start">
826 The scriptlet which will be executed after network-interfaces were
827 enabled and the directories mounted, but before the vserver itself has
828 been started. Before executing the script, the vserver root directory
829 will be made the working directory.
832 <parameter name="vserver-dir">
834 The configuration directory of the current vserver.
837 <parameter name="vserver-name">
839 The name of the current vserver.
842 <parameter name="action">
844 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
849 <collection name="pre-start.d">
851 Repository of pre-start like scripts. Before executing these scripts,
852 the vserver root directory will be made the working directory.
854 <program name="script" type="symbolic">
855 <description>See pre-start.</description>
857 <parameter name="vserver-dir">
859 The configuration directory of the current vserver.
862 <parameter name="vserver-name">
863 <description>The name of the current vserver.</description>
865 <parameter name="action">
867 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
875 <program name="post-start">
877 The scriptlet which will be executed after the vserver has been
878 started. Before executing the script, the vserver root directory
879 will be made the working directory.
882 <parameter name="vserver-dir">
883 <description>The configuration directory of the current vserver.</description>
885 <parameter name="vserver-name">
886 <description>The name of the current vserver.</description>
888 <parameter name="action">
890 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
895 <collection name="post-start.d">
897 Repository of post-start like scripts. Before executing these scripts,
898 the vserver root directory will be made the working directory.
900 <program name="script" type="symbolic">
901 <description>See post-start.</description>
903 <parameter name="vserver-dir">
904 <description>The configuration directory of the current vserver.</description>
906 <parameter name="vserver-name">
907 <description>The name of the current vserver.</description>
909 <parameter name="action">
911 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
919 <program name="pre-stop">
921 The scriptlet which will be executed before the vserver will be
922 stopped. Before executing the script, the vserver root directory
923 will be made the working directory.
926 <parameter name="vserver-dir">
927 <description>The configuration directory of the current vserver.</description>
929 <parameter name="vserver-name">
930 <description>The name of the current vserver.</description>
932 <parameter name="action">
934 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
939 <collection name="pre-stop.d">
941 Repository of pre-stop like scripts. Before executing the script, the
942 vserver root directory will be made the working directory.
944 <program name="script" type="symbolic">
945 <description>See pre-stop.</description>
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'...).
962 <program name="post-stop">
964 The scriptlet which will be executed after the vserver has been
965 stopped, but before the directories will be umounted and the the
966 interfaces disabled. Before executing the script, the vserver root
967 directory will be made the working directory.
970 <parameter name="vserver-dir">
971 <description>The configuration directory of the current vserver.</description>
973 <parameter name="vserver-name">
974 <description>The name of the current vserver.</description>
976 <parameter name="action">
978 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
983 <collection name="post-stop.d">
985 Repository of post-stop like scripts. Before executing the script, the
986 vserver root directory will be made the working directory.
988 <program name="script" type="symbolic">
989 <description>See post-stop.</description>
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'...).
1006 <program name="postpost-stop">
1008 The scriptlet which will be executed after the vserver has been stopped
1009 completely. Before executing the script, the vserver root directory
1010 will be made the working directory.
1013 <parameter name="vserver-dir">
1014 <description>The configuration directory of the current vserver.</description>
1016 <parameter name="vserver-name">
1017 <description>The name of the current vserver.</description>
1019 <parameter name="action">
1021 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1026 <collection name="postpost-stop.d">
1028 Repository of postpost-stop like scripts. Before executing the script,
1029 the vserver root directory will be made the working directory.
1031 <program name="script" type="symbolic">
1032 <description>See postpost-stop.</description>
1034 <parameter name="vserver-dir">
1035 <description>The configuration directory of the current vserver.</description>
1037 <parameter name="vserver-name">
1038 <description>The name of the current vserver.</description>
1040 <parameter name="action">
1042 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1050 <collection name="interfaces">
1051 <scalar name="bcast">
1052 <description>The default broadcast address.</description>
1055 <description>The default network device.</description>
1057 <scalar name="prefix">
1058 <description>The default network prefix-length.</description>
1060 <scalar name="mask">
1061 <description>The default network mask.</description>
1063 <scalar name="scope">
1064 <description>The default scope of the network interfaces.</description>
1067 <collection name="iface" type="symbolic">
1069 'iface' is an arbitrary name for the interface; the value itself is
1070 not important but may be interesting regarding interface-creation and
1071 usage with <tool>chbind</tool>. Both happens in alphabetical order and
1072 numbers like '00' are good names for these directories.
1075 <boolean name="disabled">
1076 <description>When this file exists, this interface will be ignored.</description>
1080 <description>The ip which will be assigned to this interface.</description>
1082 <scalar name="bcast">
1083 <description>The broadcast address.</description>
1086 <description>The network device.</description>
1088 <scalar name="prefix">
1089 <description>The network prefix-length.</description>
1091 <scalar name="mask">
1092 <description>The network mask.</description>
1094 <scalar name="scope">
1095 <description>The scope of the network interface.</description>
1097 <scalar name="name">
1099 When this file exists, the interface will be named with the text in
1100 this file. Without such an entry, the IP will not be shown by
1101 <tool>ifconfig</tool> but by <command>ip addr ls</command> only. Such
1102 a labeled interface is known as an "alias" also (e.g. 'eth0:foo').
1105 <boolean name="nodev">
1107 When this file exists, the interface will be assumed to exist
1108 already. This can be used to assign primary interfaces which are
1109 created by the host or another vserver.
1112 <boolean name="novlandev">
1114 When this file exists, the steps which setup and destroy a VLAN
1115 interface will be skipped. This flag should be set when a VLAN
1116 interface is used by multiple vservers or by the host.
1122 <collection name="ulimits">
1124 A directory with ulimits. Possible resources are cpu, data, fsize,
1125 locks, memlock, nofile, nproc, rss and/or stack. This configuration
1126 will be honored for kernel 2.4 only.
1128 <scalar name="resource" type="symbolic">
1130 A file which contains the hard- and soft-limit of the given resource
1131 in the first line. The special keyword 'inf' is recognized.
1134 <scalar name="resource.hard" type="symbolic">
1136 A file which contains the hard- of the given resource in the first
1137 line. The special keyword 'inf' is recognized.
1140 <scalar name="resource.soft" type="symbolic">
1142 A file which contains the soft- of the given resource in the first
1143 line. The special keyword 'inf' is recognized.
1148 <collection name="rlimits">
1150 A directory with resource limits. Possible resources are cpu, fsize,
1151 data, stack, core, rss, nproc, nofile, memlock, as and locks. This
1152 configuration will be honored for kernel 2.6 only.
1154 <scalar name="resource" type="symbolic">
1156 A file which contains the hard- and soft-limit of the given resource
1157 in the first line. The special keyword 'inf' is recognized.
1160 <scalar name="resource.hard" type="symbolic">
1162 A file which contains the hard- of the given resource in the first
1163 line. The special keyword 'inf' is recognized.
1166 <scalar name="resource.soft" type="symbolic">
1168 A file which contains the soft- of the given resource in the first
1169 line. The special keyword 'inf' is recognized.
1172 <scalar name="resource.min" type="symbolic">
1174 A file which contains the guaranted minimum of the given resource in
1175 the first line. The special keyword 'inf' is recognized.
1180 <collection name="uts">
1181 <scalar name="context">
1183 The context-name of the vserver. This file is listed for completeness
1184 only; the 'context' name is used and set internally by the util-vserver
1185 tools and can *not* be modified.
1188 <scalar name="sysname">
1189 <description>The sysname of the vserver</description>
1191 <scalar name="nodename">
1192 <description>The node-/hostname of the vserver</description>
1194 <scalar name="release">
1195 <description>The OS-release of the vserver</description>
1197 <scalar name="version">
1198 <description>The OS-version of the vserver</description>
1200 <scalar name="machine">
1201 <description>The machine-type of the vserver</description>
1203 <scalar name="domainname">
1204 <description>The NIS domainname of the vserver</description>
1208 <collection name="dlimits">
1209 <collection name="dlimit" type="symbolic">
1210 <scalar name="directory">
1211 <description>The directory to which the limit should be applied</description>
1213 <scalar name="inodes_total">
1214 <description>The amount of inodes this vserver should be limited to</description>
1216 <scalar name="space_total">
1217 <description>The amount of space this vserver should be limited to (measured in blocks of 1024 bytes)</description>
1219 <scalar name="reserved">
1220 <description>How much space (percentage-wise) should be reserved for the root user</description>
1225 <collection name="cpuset">
1226 <scalar name="name">
1227 <description>The name of the cpuset for this vserver</description>
1229 <scalar name="cpus">
1230 <description>The list of CPUs in this cpuset</description>
1232 <scalar name="mems">
1233 <description>The list of Memory Nodes in this cpuset</description>
1235 <scalar name="cpu_exclusive">
1236 <description>Is the CPU assignment exclusive?</description>
1238 <scalar name="mems_exclusive">
1239 <description>Is the memory node assignment exclusive?</description>
1241 <scalar name="nocreate">
1242 <description>When this file exists, the cpuset will be assumed to exist already</description>