X-Git-Url: http://git.linux-vserver.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fconfiguration.xml;h=fc7416fadd4a11f1745b6b9ddbaac62c4ee40c69;hb=be41237a12dad904d92e58373f670113bb730a24;hp=8db75d18fcbc3616bc32aec78eb3fa8b84f7a338;hpb=fac60eed96dfe149b45fd4e2b25ce4bc23de6829;p=util-vserver.git
diff --git a/doc/configuration.xml b/doc/configuration.xml
index 8db75d1..fc7416f 100644
--- a/doc/configuration.xml
+++ b/doc/configuration.xml
@@ -305,6 +305,51 @@ interface will be executed.
The default /etc/resolv.conf file.
+
+
+
+This directory contains cgroup settings which should be applied to all guests.
+See your kernel documentation for what settings are valid with your
+configuration.
+
+
+
+The directory to mount the cgroup hierarchy at. The default is /dev/cgroup.
+
+
+
+
+List of subsystems to enable on the cgroup mount point. The default is "all".
+
+
+
+
+Some subsystems start out with clean slates, making it impossible to use the
+cgroup before certain things have been set. This is true for e.g. the cpuset
+subsystem. This file contains a list of filenames which should be explicitly
+inherited from the parent (root) cgroup, if not overridden elsewhere.
+The default is cpuset.cpus and cpuset.mems.
+
+
+
+
+If this file exists, all guests will be put in one cgroup named after the
+contents of this file. The default is to put each guest in a cgroup named the
+same thing as the guest.
+
+
+
+
+If this file exists, all cgroups will be created underneath this directory
+in the cgroup mount point.
+
+
+
+
+If this file exists, each subsystem will have its own mount point.
+
+
+
@@ -467,6 +512,13 @@ url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/ncaps-net.c">lib/nc
for possible values.
+
+
+Contains the namespaces allowed to be unshared. See lib/umask-v23.c
+for possible values.
+
+
@@ -581,51 +633,17 @@ is the personality-type followed by flags (one item per line). See
values.
-
+
Contains per line a flag. See lib/cflags-v13.c
for possible values.
-
+
+
+
+Old name for cflags. Deprecated.
+
@@ -636,9 +654,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
@@ -656,6 +684,11 @@ called as chbind <options> mount .... See
fstab also.
+
+
+Contains the bias to be applied to processes in this guest when the OOM-killer strikes.
+
+
@@ -770,7 +803,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
@@ -1211,10 +1271,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.
@@ -1253,13 +1316,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.
@@ -1299,6 +1359,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.
+
+
@@ -1389,7 +1495,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. integers
The directory to which the limit should be applied
@@ -1418,6 +1528,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
@@ -1503,5 +1616,50 @@ 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)).
+
+
+
+
+
+This directory contains cgroup settings to be applied to this guest.
+See your kernel documentation for what settings are valid with your
+configuration.
+
+
+
+If this file exists, the guest will be put in a cgroup named after the
+contents of this file. The default is to name the cgroup the same thing as the
+guest, unless
+.defaults/cgroup/name says
+otherwise.
+
+
+
+
+
+If this file exists,
+.defaults/cgroup will be ignored
+for this guest.
+
+