X-Git-Url: http://git.linux-vserver.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fconfiguration.xml;h=4e998bee089bd87684b7bcdad7f5eef8fc572428;hb=93b6ce372f2e185af3cbb19d9c7620486f433496;hp=66cc7a889e68bcc3100c3eab6c8a8bdcadb5b774;hpb=aa15243daa34c99bad7be2d28fc6100d1459005e;p=util-vserver.git
diff --git a/doc/configuration.xml b/doc/configuration.xml
index 66cc7a8..4e998be 100644
--- a/doc/configuration.xml
+++ b/doc/configuration.xml
@@ -62,6 +62,34 @@ NOTE: this link exists in 0.30.202+ only; in previous versions it was
a vserver specific setting.
+
+
+
+Contains the pathname of the shell which will be used by the "vserver
+... enter" command. Can be overridden by the
+per-guest shell.
+
+
+
+
+
+The default fstab file to put in newly built guests.
+
+
+
+
+
+If this file exists, kernel-side dynamic contexts will be used by the "vserver
+... build" command. Otherwise a context will be generated, based on the
+contents of context.next.
+
+
+
+
+
+The context id to use for the next guest created by "vserver ... build".
+
+
@@ -89,6 +117,33 @@ from this uri and install it at a temporary place.
+
+
+ 'x' is an arbitrary name, replace it with e.g. device names
+
+ When this file exists, the device can be opened
+
+
+ When this file exists, the device can be created (if the guest has CAP_MKNOD)
+
+
+
+When this file exists, target will
+have to exist as well and opening the device will in fact open the target device
+
+
+
+ This file will let you specify unimplemented flags manually
+
+
+ Contains the name of a device node
+
+
+ Contains the device node of the target node to open instead of the device when remap is set
+
+
+
+
@@ -101,7 +156,7 @@ is invoked from the kernel. This should point somewhere e.g. into
-See vshelper/action.
+See vshelper/action.
@@ -204,6 +259,14 @@ When this file exists, vlogin isn't used on vserver <guest> enter.
+
+
+
+
+A list of default options to supply to vserver ... build, one option per line.
+
+
+
@@ -214,6 +277,34 @@ interface will be executed.
+
+
+ This directory contains some files which will be copied to the guests during build.
+
+ The default /etc/hosts file.
+
+
+ The default /etc/nsswitch.conf file.
+
+
+ The default /etc/krb5.conf file.
+
+
+ The default /etc/krb.conf file.
+
+
+ The default /etc/krb.realms file.
+
+
+ The default /etc/ldap.conf file.
+
+
+ The default /etc/localtime file.
+
+
+ The default /etc/resolv.conf file.
+
+
@@ -321,6 +412,11 @@ this distribution.
+
+
+Symlink to the default template for this distribution.
+
+
@@ -364,6 +460,13 @@ url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/ccaps-v13.c">lib/cc
for possible values.
+
+
+Contains the network capabilities. See lib/ncaps-net.c
+for possible values.
+
+
@@ -464,7 +567,7 @@ Contains per line a capability. This file is used for the 2.4 kernel
only; for 2.6 use bcapabilities.
-
+
Contains the pathname of the shell which will be used by the "vserver
... enter" command.
@@ -524,11 +627,28 @@ Apply the current ulimit to the whole context
-->
+
+
+Contains a network flag per line. See lib/nflags-net.c
+for possible values.
+
+
-Contains the context which shall be used for the vserver.
+Contains the context id which shall be used for the vserver. Valid range is 2 through 49151.
+
+
+Contains the network context id which shall be used for the vserver. Valid range is 2 through 49151.
+
+
+
+
+Contains the filesystem tag which shall be used for the vserver. Valid range is 2 through 49151.
+
+
The fstab file for the vserver. Entries in this file will be mounted
@@ -541,11 +661,16 @@ the 'fstab' file should be used.
The fstab file for the vserver. Entries in this file will be mounted
-within the network context of the host; this means that mount will be
+within the network context of the guest; this means that mount will be
called as chbind <options> mount .... See
fstab also.
+
+
+Contains the bias to be applied to processes in this guest when the OOM-killer strikes.
+
+
@@ -660,7 +785,34 @@ pair per line.
-
+
+
+
+ 'x' is an arbitrary name, replace it with e.g. device names
+
+ When this file exists, the device can be opened
+
+
+ When this file exists, the device can be created (if the guest has CAP_MKNOD)
+
+
+
+When this file exists, target will
+have to exist as well and opening the device will in fact open the target device
+
+
+
+ This file will let you specify unimplemented flags manually
+
+
+ Contains the name of a device node
+
+
+ Contains the device node of the target node to open instead of the device when remap is set
+
+
+
+
30
@@ -671,7 +823,7 @@ assumed.
-
+ restart
The action which is going to be executed when a vshelper event
@@ -728,7 +880,7 @@ skipped.
-See vshelper/action.
+See vshelper/action.
@@ -1101,10 +1253,13 @@ The name of the current vserver.
- The default broadcast address.
+ The guest's broadcast address.
+
+
+ The guest's loopback address.
- The default network device.
+ The default network device. See iface/dev for more information.The default network prefix-length.
@@ -1143,13 +1298,10 @@ numbers like '00' are good names for these directories.
- The ip which will be assigned to this interface.
+ The IP address which will be assigned to this interface.
-
- The broadcast address.
-
-
- The network device.
+
+ The network device. When this is specified, the IP address will be assigned and removed when starting and stopping the guest.The network prefix-length.
@@ -1279,7 +1431,11 @@ tools and can *not* be modified.
-
+
+Note that all entries are required for the disk limit to be applied.
+
+
+ 'x' is an arbitrary name, replace it with e.g. integersThe directory to which the limit should be applied
@@ -1295,7 +1451,22 @@ tools and can *not* be modified.
+
+
+ 'x' is an arbitrary name, replace it with e.g. integers
+
+ The sysctl setting
+
+
+ The value
+
+
+
+
+
+Puts the guest in a cpuset. Required entries are name, cpus and mems.
+ The name of the cpuset for this vserver