X-Git-Url: http://git.linux-vserver.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fconfiguration.xml;h=fc7416fadd4a11f1745b6b9ddbaac62c4ee40c69;hb=HEAD;hp=75a7af9d484450689bf7cf3a18deebd87b6722e7;hpb=e693d7d74f636fa40aa45a15edcd64c300213d1e;p=util-vserver.git diff --git a/doc/configuration.xml b/doc/configuration.xml index 75a7af9..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. + @@ -1341,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. + + @@ -1564,5 +1628,38 @@ Puts the guest in a cpuset. Required entries are name, cpus and mems. 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. + +