X-Git-Url: http://git.linux-vserver.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fconfiguration.xml;h=729a19716d8869a17efb70b719a6f491753383a1;hb=443949610f23ce8e4c9764728f21d7bef968d14f;hp=967e2333b2c1d52a37dfc9732227a37850422b5c;hpb=8c969ef86ca0c4aff7dd1d1dc483dc9cd10c79bd;p=util-vserver.git
diff --git a/doc/configuration.xml b/doc/configuration.xml
index 967e233..729a197 100644
--- a/doc/configuration.xml
+++ b/doc/configuration.xml
@@ -76,6 +76,20 @@ Contains the pathname of the shell which will be used by the "vserver
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".
+
+
@@ -398,6 +412,11 @@ this distribution.
+
+
+Symlink to the default template for this distribution.
+
+
@@ -617,9 +636,19 @@ 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
@@ -632,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.
+
+
@@ -751,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
@@ -1192,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.
@@ -1234,13 +1298,10 @@ numbers like '00' are good names for these directories.
- The ip which will be assigned to this interface.
-
-
- The broadcast address.
+ The IP address which will be assigned to this interface.
-
- 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.
@@ -1280,6 +1341,52 @@ When this file exists, the steps which setup and destroy a VLAN
interface will be executed.
+
+
+When this file exists, a tun interface will be created when the guest
+starts, and removed when the guest stops.
+
+
+
+
+When this file exists, a tap interface will be created when the guest
+starts, and removed when the guest stops.
+
+
+
+
+If a tun or tap interface is created, the presence of this file will
+disable checksumming on it.
+
+
+
+
+When this file exists, the tun/tap interface created will not be
+owned by this particular guest.
+
+
+
+
+Sets the ownership of tun/tap interfaces. Requires a user id, not a
+username.
+
+
+
+
+Sets the group ownership of tun/tap interfaces. Requires a group id,
+not a group name.
+
+
+
+
+Sets the link type of tun/tap interfaces.
+
+
+
+
+Sets the peer for a point-to-point link, such as a tun interface.
+
+
@@ -1370,7 +1477,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
@@ -1399,6 +1510,9 @@ tools and can *not* be modified.
+
+Puts the guest in a cpuset. Required entries are name, cpus and mems.
+ The name of the cpuset for this vserver
@@ -1484,5 +1598,26 @@ tools and can *not* be modified.
+
+
+
+ Enables pid virtualization for this guest
+
+
+ Enable network virtualization for this guest
+
+
+ Contains a mask of spaces to clone/enter
+
+
+
+
+
+ The IO scheduling class to use for this guest (see ionice(1)).
+
+
+ The IO scheduling priority to use for this guest (see ionice(1)).
+
+