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.
195 <collection name="interfaces" use="optional">
196 <boolean id="global-vlandev" name="vlandev">
198 When this file exists, the steps which setup and destroy a VLAN
199 interface will be executed.
205 <collection name=".distributions" use="optional">
206 <collection name="dist" type="symbolic">
208 <description></description>
210 <collection name="yum">
212 The default, yum-related content of the <directory>/etc</directory>
215 <scalar name="yum.conf">
217 The master yum configuration file. It supports the @YUMETCDIR@,
218 @YUMCACHEDIR@ and @YUMLOGDIR@ placeholder which will be replaced at
219 <command>vserver ... build</command> time.
223 <collection name="yum.repos.d">
224 <description>A directory with yum repositories.</description>
226 <data name="apt.conf">
228 The default apt.conf which is going to be used. It overrides the
229 apt.conf from CONFDIR/.defaults/apps/pkgmgmt.
232 <program name="initpre">
234 Script which will be executed before packages will be installed.
237 <parameter name="confdir">
239 The configuration directory of the vserver which is going to be set up.
242 <parameter name="vserver">
244 The pathname of the vserver binary.
249 <program name="initpost">
251 Script which will be executed after packages are installed.
254 <parameter name="confdir">
256 The configuration directory of the vserver which is going to be set up.
259 <parameter name="vserver">
261 The pathname of the vserver binary.
267 <collection name="pkgs">
269 Contains files with packagenames.
273 File which contains the name of packages. On top of file the special
274 keywords '--reinstall' and '--can-fail' are possible.
279 <collection name="pubkeys">
281 Directory with GPG pubkeys which are used to sign the packages of this
286 <collection name="apt">
288 Default content of the <directory>/etc/apt/</directory> directory.
292 <collection name="rpm">
294 Default content of the <directory>/etc/rpm</directory> directory.
300 Directory which overrides <directory>/usr/lib/rpm</directory>.
303 <link name="execdir">
305 Directory with all executables and libraries which are required for
312 <!-- Vserver configuration -->
313 <collection name="vserver-name" type="symbolic">
315 The configuration directory for the vserver vserver-name.
319 <default>../.defaults/cachebase/VSERVERNAME</default>
321 Path of the storage area for cached information about this vserver.
326 <default>../.defaults/vdirbase/VSERVERNAME</default>
328 Path of the vserver root directory
334 Points to a file which will contain the XID of the running vserver. When
335 the vserver is stopped, this can be a dangling symlink.
339 <list id="bcapabilities" name="bcapabilities">
341 [experimental; name is subject of possible change] Contains the system capabilities. See
342 <ulink url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/bcaps-v13.c?rev=HEAD">lib/bcaps-v13.c</ulink>
346 <list name="ccapabilities">
348 [experimental; name is subject of possible change] Contains the
349 context capabilities. See <ulink
350 url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/ccaps-v13.c?rev=HEAD">lib/ccaps-v13.c</ulink>
355 <boolean id="global-namespace" name="namespace">
357 Overrides the global <optionref ref="global-nonamespace">nonamespace</optionref> flag and enables
358 namespace usage for the current vserver.
362 <boolean name="nonamespace">
364 Disables namespace usage for the current vserver.
366 In this mode the <directory>/vservers</directory> directory must have
367 the 'barrier' attribute. Else, common chroot(2) exploits are possible.
371 <boolean id="global-nonamespace-cleanup" name="nonamespace-cleanup">
373 Overrides the global <optionref ref="global-namespace-cleanup">namespace-cleanup</optionref> flag and disables
374 namespace cleanup for the current vserver.
378 <boolean name="namespace-cleanup">
380 Enable namespace cleanup for the current vserver.
384 <hash name="schedule">
386 [experimental; name is subject of possible change] Contains the
387 scheduler parameters, one per line.
389 The Hard CPU limit uses a mechanism called a Token Bucket. the
390 concept is simple: you have a bucket of a certain size which is
391 filled with a specified amount R of tokens each interval T until the
392 maximum is reached (excess tokens are spilled). At each timer tick,
393 a running process consumes one token from the bucket, unless the
394 bucket is empty. If the bucket is empty the process is put in the
395 hold queue. When the bucket has been refilled to at least M tokens,
396 all on hold processes are rescheduled.
398 See the <ulink url="http://linux-vserver.org/Scheduler+Parameters">Linux
399 VServer Wiki</ulink> for more information about this file.
402 <key id="fill_rate" name="fill-rate">
404 Amount of tokens append to the bucket each interval.
407 <key name="interval">
409 The intervall between refills of amount <optionref>fill_rate</optionref>. This
410 value is express in ticks.
415 Initial bucket contents.
418 <key name="tokens-min">
420 The minimum amount of tokens required to unhold processes
423 <key name="tokens-max">
428 <key name="priority-bias">
437 Contains the name of the vserver. When not given, the basename of the directory
438 will be assumed as this name.
443 The nice-level on which the vserver will be started.
446 <list name="capabilities">
448 Contains per line a capability. This file is used for the 2.4 kernel
449 only; for 2.6 use <optionref>bcapabilities</optionref>.
452 <scalar name="shell">
454 Contains the pathname of the shell which will be used by the "vserver
458 <list name="personality">
460 Used to set the personality of the vserver. First line in the file
461 is the personality-type followed by flags (one item per line). See
462 <filename>/usr/include/linux/personality.h</filename> for possible
468 Contains per line a flag. See <ulink
469 url="http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/cflags-v13.c?rev=HEAD">lib/cflags-v13.c</ulink>
474 <element name="fakeinit">
476 The new process will believe it is process number 1. Useful to run a
477 real /sbin/init in a vserver. Warning: this flag should not be used
478 unless you know what you are doing. Often, it is better to use the
482 <element name="lock">
484 The new process is trapped and can't use chcontext anymore.
487 <element name="sched">
489 The new process and its children will share a common
492 <element name="nproc">
494 Limit the number of process in the vserver according to
495 ulimit setting. Normally, ulimit is a per user thing.
496 With this flag, it becomes a per vserver thing.
499 <element name="private">
501 No one can join this security context once created.
504 <element name="ulimit">
506 Apply the current ulimit to the whole context
512 <scalar name="context">
514 Contains the context which shall be used for the vserver.
517 <data id="fstab" name="fstab">
519 The fstab file for the vserver. Entries in this file will be mounted
520 within the network context of the host. Use the
521 <optionref>fstab.remote</optionref> file when you want that the
522 mounting happens in the network context of the vserver. In most cases
523 the 'fstab' file should be used.
526 <data id="fstab.remote" name="fstab.remote">
528 The fstab file for the vserver. Entries in this file will be mounted
529 within the network context of the host; this means that mount will be
530 called as <command>chbind <options> mount ...</command>. See
531 <optionref>fstab</optionref> also.
535 <collection name="apps">
536 <collection name="init">
539 The initial-mtab which will be used for the vserver.
543 <scalar name="style">
545 Contains the init-style.
548 <enumeration value="sysv"/>
549 <enumeration value="plain"/>
550 <enumeration value="minit"/>
551 <enumeration value="gento"/>
555 <scalar name="runlevel">
556 <description>The start runlevel.</description>
559 <scalar name="runlevel.start">
560 <description>The start runlevel.</description>
563 <scalar name="runlevel.stop">
564 <description>The stop runlevel.</description>
567 <scalar name="killseq">
569 Contains the 'signal [wait signal]*' sequence which is used to stop
574 <list name="cmd.start">
576 The command which is used to start the vserver. Each option must be on
581 <list name="cmd.start-sync">
583 The command which is used to wait on the vserver after it has been
584 started. 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.stop">
592 The command which is used to stop the vserver. Each option must be on
597 <list name="cmd.stop-sync">
599 The command which is used to wait on the vserver after it has been
600 stopped. Each option must be on a separate line. This file will be
601 ignored when the <optionref>sync</optionref> flag does not exist and the
602 '--sync' option was not used.
606 <list name="cmd.prepare">
608 The command which is used to setup the init-system (e.g. to set the
609 runlevel in the utmp-file). Each option must be on a separate line.
613 <boolean id="sync" name="sync">
615 If this file is not present, all 'cmd.*-sync files will be ignored.
621 A symlink to the TTY device where input/output will be redirected
622 from/to at startup via initscript.
628 This file is used to mark group of vservers which shall be started/stopped
629 together by the initscript. Content is a simple string like 'default'.
633 <list name="depends">
635 This file is used to configure vservers which must be running before
636 the current vserver can be started. At shutdown, the current vserver
637 will be stopped before its dependencies. Content of this file are
638 vserver ids (one name per line).
642 <list name="environment">
644 The environment to set when starting the guest. Contains one VAR=VAL
650 <collection name="vshelper">
651 <scalar name="sync-timeout">
652 <default>30</default>
654 The timeout in seconds which is used when synchronising vserver
655 startup/shutdown with the vshelper. When no set, 30 seconds will be
660 <scalar name="action">
661 <default>restart</default>
663 The action which is going to be executed when a vshelper event
664 occurs. The default value is 'restart', but there can be defined own
665 methods by placing scripts into the
666 <optionref>vshelper-methods</optionref> directories. These scripts are
667 fed with the same arguments as the <tool>vshelper</tool> script.
671 <program name="event" type="symbolic">
673 When existing, these scripts will be executed *instead* of the default
674 handler defined in 'action'. Their name must match the event which caused
675 the execution of <tool>vshelper</tool>; e.g. 'restart' or 'poweroff'. See
676 the vs_reboot() function in the kernel for more details.
679 <parameter name="xid">
681 The xid of the context calling the vshelper
684 <parameter name="event">
692 <boolean name="disabled">
694 When existing, the vshelper functionality will be disabled for this
699 <boolean name="debug">
701 When existing, the vshelper execution will be traced for this vserver.
705 <boolean name="warning-disabled">
707 When existing, sanity checks for the vshelper functionality will be
714 <collection id="vshelper-methods" name="vshelper-methods">
715 <program name="handler" type="symbolic">
722 <collection name="vunify">
724 This directory contains configuration data required for vserver
728 <list name="exclude">
730 <p>Static list of files which are excluded for unification. This list
731 supports an rsync-like syntax: when a file is prefixed by '+', it is a
732 candidate for unification; when there is no prefix or a '-' or a '~' it
733 will be excluded. Shell-wildcards are allowed for the filenames.</p>
734 <p>When used with <tool>vcopy</tool>, the '~' prefix prevents copying
735 of the file entirely (e.g. for keyfiles). With this tool, the file will
736 be copied instead of hardlinked when the '-' prefix is used.</p>
740 <link name="refserver.X" type="symbolic">
742 These are symlinks to the configuration directory
743 (e.g. CONFDIR/vservers/<id>) of a refserver. There may be
744 multiple such symlinks but they must be prefixed by 'refserver.' and
745 will be processed in alphanumerical order.
749 <collection name="hash" since="0.30.205">
751 A directory which will be used as the storage place for the
752 <tool>vhashify</tool> command.
754 <link name="id" type="symbolic">
756 Points to a directory within the filesystems which are used for the
757 vservers. There must be not more than one of such a directory per
762 <scalar name="method" since="0.30.299">
763 <default>SHA1</default>
764 <description>The used hash method.</description>
768 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205">
770 When existing, information from packagemanagement will not be used to
771 create dynamic exclude-lists.
775 <boolean name="pgkmgmt-force" default="off" since="0.30.205">
777 When existing, information from packagemanagement will be used to
778 create dynamic exclude-lists. This option requires that (a known)
779 packagemanagement is configured for the vserver; else the requested
780 operation will fail. Most tools assume 'on' as the default value.
787 <collection name="scripts">
789 A directory for scripts. By default, when one of these scripts will be
790 executed, the execution of defaultscripts (within .../.defaults/scripts)
791 will be skipped. To execute them nevertheless, the $DONT_SKIP_DEFAULTS
792 environment variable must be set by one of the in-shellcontext scripts
793 (the non-executable ones).
796 <program name="initialize">
798 The scriptlet which will be executed before the root filesystem is mounted and
799 the configuration has been loaded. Before executing the script, the
800 configuration directory will be made the working directory.
803 <parameter name="vserver-dir">
805 The configuration directory of the current vserver.
808 <parameter name="vserver-name">
810 The name of the current vserver.
813 <parameter name="action">
815 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
820 <collection name="initialize.d">
822 Repository of initialize like scripts. Before executing the script,
823 the configuration directory will be made the working directory.
825 <program name="script" type="symbolic">
826 <description>See initialize.</description>
828 <parameter name="vserver-dir">
830 The configuration directory of the current vserver.
833 <parameter name="vserver-name">
835 The name of the current vserver.
838 <parameter name="action">
840 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
847 <program name="prepre-start">
849 The scriptlet which will be executed before the network-interfaces are
850 enabled and the directories are mounted. Before executing the script,
851 the configuration directory will be made the working directory.
854 <parameter name="vserver-dir">
856 The configuration directory of the current vserver.
859 <parameter name="vserver-name">
861 The name of the current vserver.
864 <parameter name="action">
866 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
871 <collection name="prepre-start.d">
873 Repository of prepre-start like scripts. Before executing the script,
874 the configuration directory will be made the working directory.
876 <program name="script" type="symbolic">
877 <description>See prepre-start.</description>
879 <parameter name="vserver-dir">
881 The configuration directory of the current vserver.
884 <parameter name="vserver-name">
886 The name of the current vserver.
889 <parameter name="action">
891 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
898 <program name="pre-start">
900 The scriptlet which will be executed after network-interfaces were
901 enabled and the directories mounted, but before the vserver itself has
902 been started. Before executing the script, the vserver root directory
903 will be made the working directory.
906 <parameter name="vserver-dir">
908 The configuration directory of the current vserver.
911 <parameter name="vserver-name">
913 The name of the current vserver.
916 <parameter name="action">
918 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
923 <collection name="pre-start.d">
925 Repository of pre-start like scripts. Before executing these scripts,
926 the vserver root directory will be made the working directory.
928 <program name="script" type="symbolic">
929 <description>See pre-start.</description>
931 <parameter name="vserver-dir">
933 The configuration directory of the current vserver.
936 <parameter name="vserver-name">
937 <description>The name of the current vserver.</description>
939 <parameter name="action">
941 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
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="vserver-dir">
957 <description>The configuration directory of the current vserver.</description>
959 <parameter name="vserver-name">
960 <description>The name of the current vserver.</description>
962 <parameter name="action">
964 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
969 <collection name="post-start.d">
971 Repository of post-start like scripts. Before executing these scripts,
972 the vserver root directory will be made the working directory.
974 <program name="script" type="symbolic">
975 <description>See post-start.</description>
977 <parameter name="vserver-dir">
978 <description>The configuration directory of the current vserver.</description>
980 <parameter name="vserver-name">
981 <description>The name of the current vserver.</description>
983 <parameter name="action">
985 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
993 <program name="pre-stop">
995 The scriptlet which will be executed before the vserver will be
996 stopped. Before executing the script, the vserver root directory
997 will be made the working directory.
1000 <parameter name="vserver-dir">
1001 <description>The configuration directory of the current vserver.</description>
1003 <parameter name="vserver-name">
1004 <description>The name of the current vserver.</description>
1006 <parameter name="action">
1008 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1013 <collection name="pre-stop.d">
1015 Repository of pre-stop like scripts. Before executing the script, the
1016 vserver root directory will be made the working directory.
1018 <program name="script" type="symbolic">
1019 <description>See pre-stop.</description>
1021 <parameter name="vserver-dir">
1022 <description>The configuration directory of the current vserver.</description>
1024 <parameter name="vserver-name">
1025 <description>The name of the current vserver.</description>
1027 <parameter name="action">
1029 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1036 <program name="post-stop">
1038 The scriptlet which will be executed after the vserver has been
1039 stopped, but before the directories will be umounted and the the
1040 interfaces disabled. Before executing the script, the vserver root
1041 directory will be made the working directory.
1044 <parameter name="vserver-dir">
1045 <description>The configuration directory of the current vserver.</description>
1047 <parameter name="vserver-name">
1048 <description>The name of the current vserver.</description>
1050 <parameter name="action">
1052 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1057 <collection name="post-stop.d">
1059 Repository of post-stop like scripts. Before executing the script, the
1060 vserver root directory will be made the working directory.
1062 <program name="script" type="symbolic">
1063 <description>See post-stop.</description>
1065 <parameter name="vserver-dir">
1066 <description>The configuration directory of the current vserver.</description>
1068 <parameter name="vserver-name">
1069 <description>The name of the current vserver.</description>
1071 <parameter name="action">
1073 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1080 <program name="postpost-stop">
1082 The scriptlet which will be executed after the vserver has been stopped
1083 completely. Before executing the script, the vserver root directory
1084 will be made the working directory.
1087 <parameter name="vserver-dir">
1088 <description>The configuration directory of the current vserver.</description>
1090 <parameter name="vserver-name">
1091 <description>The name of the current vserver.</description>
1093 <parameter name="action">
1095 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1100 <collection name="postpost-stop.d">
1102 Repository of postpost-stop like scripts. Before executing the script,
1103 the vserver root directory will be made the working directory.
1105 <program name="script" type="symbolic">
1106 <description>See postpost-stop.</description>
1108 <parameter name="vserver-dir">
1109 <description>The configuration directory of the current vserver.</description>
1111 <parameter name="vserver-name">
1112 <description>The name of the current vserver.</description>
1114 <parameter name="action">
1116 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...).
1124 <collection name="interfaces">
1125 <scalar name="bcast">
1126 <description>The default broadcast address.</description>
1129 <description>The default network device.</description>
1131 <scalar name="prefix">
1132 <description>The default network prefix-length.</description>
1134 <scalar name="mask">
1135 <description>The default network mask.</description>
1137 <scalar name="scope">
1138 <description>The default scope of the network interfaces.</description>
1140 <boolean id="local-vlandev" name="vlandev">
1142 When this file exists, the steps which setup and destroy a VLAN
1143 interface will be executed for all interfaces of this vserver.
1146 <boolean id="local-novlandev" name="novlandev">
1148 When this file exists, the steps which setup and destroy a VLAN
1149 interface will be skipped. This overrides the global
1150 <optionref ref="global-vlandev">vlandev</optionref> setting for
1155 <collection name="iface" type="symbolic">
1157 'iface' is an arbitrary name for the interface; the value itself is
1158 not important but may be interesting regarding interface-creation and
1159 usage with <tool>chbind</tool>. Both happens in alphabetical order and
1160 numbers like '00' are good names for these directories.
1163 <boolean name="disabled">
1164 <description>When this file exists, this interface will be ignored.</description>
1168 <description>The ip which will be assigned to this interface.</description>
1170 <scalar name="bcast">
1171 <description>The broadcast address.</description>
1174 <description>The network device.</description>
1176 <scalar name="prefix">
1177 <description>The network prefix-length.</description>
1179 <scalar name="mask">
1180 <description>The network mask.</description>
1182 <scalar name="scope">
1183 <description>The scope of the network interface.</description>
1185 <scalar name="name">
1187 When this file exists, the interface will be named with the text in
1188 this file. Without such an entry, the IP will not be shown by
1189 <tool>ifconfig</tool> but by <command>ip addr ls</command> only. Such
1190 a labeled interface is known as an "alias" also (e.g. 'eth0:foo').
1193 <boolean name="nodev">
1195 When this file exists, the interface will be assumed to exist
1196 already. This can be used to assign primary interfaces which are
1197 created by the host or another vserver.
1200 <boolean name="novlandev">
1202 When this file exists, the steps which setup and destroy a VLAN
1203 interface will be skipped. This will override the global
1204 <optionref ref="global-vlandev">vlandev</optionref> and the per-guest
1205 <optionref ref="local-vlandev">vlandev</optionref>.
1208 <boolean name="vlandev">
1210 When this file exists, the steps which setup and destroy a VLAN
1211 interface will be executed.
1217 <collection name="ulimits">
1219 A directory with ulimits. Possible resources are cpu, data, fsize,
1220 locks, memlock, nofile, nproc, rss and/or stack. This configuration
1221 will be honored for kernel 2.4 only.
1223 <scalar name="resource" type="symbolic">
1225 A file which contains the hard- and soft-limit of the given resource
1226 in the first line. The special keyword 'inf' is recognized.
1229 <scalar name="resource.hard" type="symbolic">
1231 A file which contains the hard- of the given resource in the first
1232 line. The special keyword 'inf' is recognized.
1235 <scalar name="resource.soft" type="symbolic">
1237 A file which contains the soft- of the given resource in the first
1238 line. The special keyword 'inf' is recognized.
1243 <collection name="rlimits">
1245 A directory with resource limits. Possible resources are cpu, fsize,
1246 data, stack, core, rss, nproc, nofile, memlock, as and locks. This
1247 configuration will be honored for kernel 2.6 only.
1249 <scalar name="resource" type="symbolic">
1251 A file which contains the hard- and soft-limit of the given resource
1252 in the first line. The special keyword 'inf' is recognized.
1255 <scalar name="resource.hard" type="symbolic">
1257 A file which contains the hard- of the given resource in the first
1258 line. The special keyword 'inf' is recognized.
1261 <scalar name="resource.soft" type="symbolic">
1263 A file which contains the soft- of the given resource in the first
1264 line. The special keyword 'inf' is recognized.
1267 <scalar name="resource.min" type="symbolic">
1269 A file which contains the guaranted minimum of the given resource in
1270 the first line. The special keyword 'inf' is recognized.
1275 <collection name="uts">
1276 <scalar name="context">
1278 The context-name of the vserver. This file is listed for completeness
1279 only; the 'context' name is used and set internally by the util-vserver
1280 tools and can *not* be modified.
1283 <scalar name="sysname">
1284 <description>The sysname of the vserver</description>
1286 <scalar name="nodename">
1287 <description>The node-/hostname of the vserver</description>
1289 <scalar name="release">
1290 <description>The OS-release of the vserver</description>
1292 <scalar name="version">
1293 <description>The OS-version of the vserver</description>
1295 <scalar name="machine">
1296 <description>The machine-type of the vserver</description>
1298 <scalar name="domainname">
1299 <description>The NIS domainname of the vserver</description>
1303 <collection name="dlimits">
1304 <collection name="dlimit" type="symbolic">
1305 <scalar name="directory">
1306 <description>The directory to which the limit should be applied</description>
1308 <scalar name="inodes_total">
1309 <description>The amount of inodes this vserver should be limited to</description>
1311 <scalar name="space_total">
1312 <description>The amount of space this vserver should be limited to (measured in blocks of 1024 bytes)</description>
1314 <scalar name="reserved">
1315 <description>How much space (percentage-wise) should be reserved for the root user</description>
1320 <collection name="cpuset">
1321 <scalar name="name">
1322 <description>The name of the cpuset for this vserver</description>
1324 <scalar name="cpus">
1325 <description>The list of CPUs in this cpuset</description>
1327 <scalar name="mems">
1328 <description>The list of Memory Nodes in this cpuset</description>
1330 <scalar name="cpu_exclusive">
1331 <description>Is the CPU assignment exclusive?</description>
1333 <scalar name="mems_exclusive">
1334 <description>Is the memory node assignment exclusive?</description>
1336 <scalar name="nocreate">
1337 <description>When this file exists, the cpuset will be assumed to exist already</description>