configuration.xml (59224B)
1 <?xml version="1.0" encoding="UTF-8"?> 2 <!DOCTYPE database SYSTEM "configuration.dtd" []> 3 <!-- $Id$ --> 4 5 <database xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 6 xsi:noNamespaceSchemaLocation="file:configuration.xsd"> 7 8 <!-- Global configuration --> 9 <collection name=".defaults" use="optional"> 10 <collection name="init" type="fixed"> 11 <data name="mtab"> 12 <description>Default mtab file</description> 13 </data> 14 </collection> 15 16 <link name="vdirbase"> 17 <default>/vservers</default> 18 <description>A link to the default vserver rootdirectory.</description> 19 </link> 20 21 <link name="cachebase"> 22 <default>/var/cache/vservers</default> 23 <description> 24 A link to the directory which will hold cached information about 25 vservers. 26 </description> 27 </link> 28 29 <boolean id="global-nonamespace" name="nonamespace"> 30 <description> 31 Disable namespace usage globally. It can be overridden for a single vserver 32 by setting the <optionref ref="global-namespace">namespace</optionref> flag 33 there. 34 35 In this mode the <directory>/vservers</directory> directory must have 36 the 'barrier' attribute. Else, common chroot(2) exploits are possible. 37 </description> 38 </boolean> 39 40 <boolean id="global-nonamespace-cleanup" name="nonamespace-cleanup"> 41 <description> 42 Disable namespace cleanup globally. It can be overridden for a single vserver 43 by setting the <optionref ref="namespace-cleanup">namespace-cleanup</optionref> flag 44 there. 45 </description> 46 </boolean> 47 48 <list id="global-namespace-cleanup-skip" name="namespace-cleanup-skip"> 49 <description> 50 List of paths to skip during namespace cleanup. 51 </description> 52 </list> 53 54 <link name="run.rev"> 55 <description> 56 Path of the vserver run reverse directory. This directory contains 57 symlinks named with XID numbers which point back to the configuration 58 directory of vservers. Under kernel 2.4 this is required for the XID 59 to VSERVER mapping; Under kernel 2.6 it is unused. 60 61 NOTE: this link exists in 0.30.202+ only; in previous versions it was 62 a vserver specific setting. 63 </description> 64 </link> 65 66 <scalar name="shell"> 67 <description> 68 Contains the pathname of the shell which will be used by the "vserver 69 ... enter" command. Can be overridden by the 70 <optionref ref="shell">per-guest shell</optionref>. 71 </description> 72 </scalar> 73 74 <data name="fstab"> 75 <description> 76 The default fstab file to put in newly built guests. 77 </description> 78 </data> 79 80 <boolean name="context.dynamic"> 81 <description> 82 If this file exists, kernel-side dynamic contexts will be used by the "vserver 83 ... build" command. Otherwise a context will be generated, based on the 84 contents of <optionref>context.next</optionref>. 85 </description> 86 </boolean> 87 88 <scalar id="context.next" name="context.next"> 89 <description> 90 The context id to use for the next guest created by "vserver ... build". 91 </description> 92 </scalar> 93 94 <collection name="apps"> 95 <collection name="pkgmgmt"> 96 <link name="base"> 97 <default>/vservers/.pkg</default> 98 </link> 99 <data name="apt.conf"> 100 <description>The default apt.conf which is going to be used. It is overridden by 101 distribution specific configuration file. 102 </description> 103 </data> 104 </collection> 105 106 <collection name="debootstrap"> 107 <scalar name="mirror"> 108 <description> 109 The Debian mirror to use with the <tool>debootstrap</tool> program 110 </description> 111 </scalar> 112 <scalar name="uri"> 113 <description> 114 When the <tool>debootstrap</tool> package is not installed; fetch it 115 from this uri and install it at a temporary place. 116 </description> 117 </scalar> 118 </collection> 119 120 <collection name="vdevmap"> 121 <collection name="x" type="sybmolic"> 122 <description>'x' is an arbitrary name, replace it with e.g. device names</description> 123 <boolean name="open"> 124 <description>When this file exists, the device can be opened</description> 125 </boolean> 126 <boolean name="create"> 127 <description>When this file exists, the device can be created (if the guest has <optionref ref="bcapabilities">CAP_MKNOD</optionref>)</description> 128 </boolean> 129 <boolean id="vdevmap-remap" name="remap"> 130 <description> 131 When this file exists, <optionref ref="vdevmap-target">target</optionref> will 132 have to exist as well and opening the device will in fact open the target device 133 </description> 134 </boolean> 135 <scalar name="flags"> 136 <description>This file will let you specify unimplemented flags manually</description> 137 </scalar> 138 <scalar name="device"> 139 <description>Contains the name of a device node</description> 140 </scalar> 141 <scalar id="vdevmap-target" name="target"> 142 <description>Contains the device node of the target node to open instead of the device when <optionref ref="vdevmap-remap">remap</optionref> is set</description> 143 </scalar> 144 </collection> 145 </collection> 146 147 <collection name="vshelper"> 148 <link name="logfile"> 149 <description> 150 The file where output will be logged to when <tool>vshelper</tool> 151 is invoked from the kernel. This should point somewhere e.g. into 152 <directory>/var/log</directory>. 153 </description> 154 </link> 155 156 <collection name="vshelper-methods"> 157 <program name="handler" type="symbolic"> 158 <description> 159 See <optionref ref="vshelper-action">vshelper/action</optionref>. 160 </description> 161 </program> 162 </collection> 163 164 <boolean name="disabled"> 165 <description> 166 When existing, the vshelper functionality will be disabled for all 167 vservers. 168 </description> 169 </boolean> 170 171 <boolean name="debug"> 172 <description> 173 When existing, the vshelper execution will be traced. 174 </description> 175 </boolean> 176 177 <boolean name="warning-disabled"> 178 <description> 179 When existing, sanity checks for the vshelper functionality will be 180 skipped. 181 </description> 182 </boolean> 183 184 </collection> 185 186 <collection name="vprocunhide"> 187 <list name="files"> 188 <description> 189 A list of files which will be made visible by vprocunhide. Wildcards are 190 allowed and anything ending in '/' will be processed recursively. When this file exists, 191 it overrides the defaults in SYSDEFAULTDIR/vprocunhide-files. The entries there must be 192 absolute filenames inclusive the leading '/proc'. 193 </description> 194 </list> 195 </collection> 196 197 <collection name="init"> 198 <link name="tty"> 199 <description> 200 A symlink to the TTY device where input/output will be redirected from/to 201 at startup via initscript. 202 </description> 203 </link> 204 205 <hash id="global-environment" name="environment" since="0.30.211"> 206 <description> 207 The environment to set when starting guests. Contains one VAR=VAL 208 pair per line. 209 </description> 210 </hash> 211 </collection> 212 213 <collection name="vunify"> 214 <list name="exclude"> 215 <description>Static list of excluded files.</description> 216 </list> 217 218 <collection name="hash" since="0.30.205"> 219 <description> 220 A directory which will be used as the storage place for the 221 <tool>vhashify</tool> command. 222 </description> 223 <link name="id" type="symbolic"> 224 <description> 225 Points to a directory within the filesystems which are used for the 226 vservers. There must be not more than one of such a directory per 227 filesystem. 228 </description> 229 </link> 230 231 <scalar name="method" since="0.30.299"> 232 <default>SHA1</default> 233 <description>The used hash method.</description> 234 </scalar> 235 </collection> 236 237 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205"> 238 <description> 239 When existing, information from packagemanagement will not be used to 240 create dynamic exclude-lists. 241 </description> 242 </boolean> 243 244 <boolean name="pgkmgmt-force" default="off" since="0.30.205"> 245 <description> 246 When existing, information from packagemanagement will be used to 247 create dynamic exclude-lists. This option requires that (a known) 248 packagemanagement is configured for the vserver; else the requested 249 operation will fail. Most tools assume 'on' as the default value. 250 </description> 251 </boolean> 252 253 </collection> 254 255 <collection name="vlogin"> 256 <boolean id="vlogin-disable" name="disable" since="0.30.212"> 257 <description> 258 When this file exists, vlogin isn't used on vserver <guest> enter. 259 </description> 260 </boolean> 261 </collection> 262 263 <collection name="build"> 264 <list name="options"> 265 <description> 266 A list of default options to supply to vserver ... build, one option per line. 267 </description> 268 </list> 269 </collection> 270 </collection> 271 272 <collection name="interfaces" use="optional"> 273 <boolean id="global-vlandev" name="vlandev" since="0.30.211"> 274 <description> 275 When this file exists, the steps which setup and destroy a VLAN 276 interface will be executed. 277 </description> 278 </boolean> 279 </collection> 280 281 <collection name="files"> 282 <description>This directory contains some files which will be copied to the guests during build.</description> 283 <data name="hosts"> 284 <description>The default /etc/hosts file.</description> 285 </data> 286 <data name="nsswitch.conf"> 287 <description>The default /etc/nsswitch.conf file.</description> 288 </data> 289 <data name="krb5.conf"> 290 <description>The default /etc/krb5.conf file.</description> 291 </data> 292 <data name="krb.conf"> 293 <description>The default /etc/krb.conf file.</description> 294 </data> 295 <data name="krb.realms"> 296 <description>The default /etc/krb.realms file.</description> 297 </data> 298 <data name="ldap.conf"> 299 <description>The default /etc/ldap.conf file.</description> 300 </data> 301 <data name="localtime"> 302 <description>The default /etc/localtime file.</description> 303 </data> 304 <data name="resolv.conf"> 305 <description>The default /etc/resolv.conf file.</description> 306 </data> 307 </collection> 308 309 <collection name="cgroup" use="optional" since="0.30.216" id="global-cgroup"> 310 <description> 311 This directory contains cgroup settings which should be applied to all guests. 312 See your kernel documentation for what settings are valid with your 313 configuration. 314 </description> 315 <scalar name="mnt"> 316 <description> 317 The directory to mount the cgroup hierarchy at. The default is /dev/cgroup. 318 </description> 319 </scalar> 320 <list name="subsys"> 321 <description> 322 List of subsystems to enable on the cgroup mount point. The default is "all". 323 </description> 324 </list> 325 <list name="inherit"> 326 <description> 327 Some subsystems start out with clean slates, making it impossible to use the 328 cgroup before certain things have been set. This is true for e.g. the cpuset 329 subsystem. This file contains a list of filenames which should be explicitly 330 inherited from the parent (root) cgroup, if not overridden elsewhere. 331 The default is cpuset.cpus and cpuset.mems. 332 </description> 333 </list> 334 <scalar name="name" id="global-cgroup-name"> 335 <description> 336 If this file exists, all guests will be put in one cgroup named after the 337 contents of this file. The default is to put each guest in a cgroup named the 338 same thing as the guest. 339 </description> 340 </scalar> 341 <scalar name="base"> 342 <description> 343 If this file exists, all cgroups will be created underneath this directory 344 in the cgroup mount point. 345 </description> 346 </scalar> 347 <boolean name="per-ss"> 348 <description> 349 If this file exists, each subsystem will have its own mount point. 350 </description> 351 </boolean> 352 </collection> 353 354 <collection name="netns" use="optional" since="0.30.216" id="global-netns"> 355 <scalar name="name"> 356 <description> 357 The name of the network namespace to use for guests. 358 </description> 359 </scalar> 360 <boolean name="shared"> 361 <description> 362 Whether or not util-vserver should add and delete the network namespace when 363 the guest is started and stopped, respectively. 364 </description> 365 </boolean> 366 </collection> 367 </collection> 368 369 <collection name=".distributions" use="optional"> 370 <collection name="dist" type="symbolic"> 371 <scalar name="dev"> 372 <description></description> 373 </scalar> 374 <collection name="yum"> 375 <description> 376 The default, yum-related content of the <directory>/etc</directory> 377 directory. 378 </description> 379 <scalar name="yum.conf"> 380 <description> 381 The master yum configuration file. It supports the @YUMETCDIR@, 382 @YUMCACHEDIR@ and @YUMLOGDIR@ placeholder which will be replaced at 383 <command>vserver ... build</command> time. 384 </description> 385 </scalar> 386 </collection> 387 <collection name="yum.repos.d"> 388 <description>A directory with yum repositories.</description> 389 </collection> 390 <data name="apt.conf"> 391 <description> 392 The default apt.conf which is going to be used. It overrides the 393 apt.conf from CONFDIR/.defaults/apps/pkgmgmt. 394 </description> 395 </data> 396 <program name="initpre"> 397 <description> 398 Script which will be executed before packages will be installed. 399 </description> 400 <parameterList> 401 <parameter name="confdir"> 402 <description> 403 The configuration directory of the vserver which is going to be set up. 404 </description> 405 </parameter> 406 <parameter name="util-vserver-vars"> 407 <description> 408 The pathname of the util-vserver-vars file. 409 </description> 410 </parameter> 411 </parameterList> 412 </program> 413 <program name="initpost"> 414 <description> 415 Script which will be executed after packages are installed. 416 </description> 417 <parameterList> 418 <parameter name="confdir"> 419 <description> 420 The configuration directory of the vserver which is going to be set up. 421 </description> 422 </parameter> 423 <parameter name="vserver"> 424 <description> 425 The pathname of the util-vserver-vars file. 426 </description> 427 </parameter> 428 </parameterList> 429 </program> 430 431 <collection name="pkgs"> 432 <description> 433 Contains files with packagenames. 434 </description> 435 <list name="list"> 436 <description> 437 File which contains the name of packages. On top of file the special 438 keywords '--reinstall' and '--can-fail' are possible. 439 </description> 440 </list> 441 </collection> 442 443 <collection name="pubkeys"> 444 <description> 445 Directory with GPG pubkeys which are used to sign the packages of this 446 distribution. 447 </description> 448 </collection> 449 450 <collection name="apt"> 451 <description> 452 Default content of the <directory>/etc/apt/</directory> directory. 453 </description> 454 </collection> 455 456 <collection name="rpm"> 457 <description> 458 Default content of the <directory>/etc/rpm</directory> directory. 459 </description> 460 </collection> 461 462 <link name="rpmlib"> 463 <description> 464 Directory which overrides <directory>/usr/lib/rpm</directory>. 465 </description> 466 </link> 467 <link name="execdir"> 468 <description> 469 Directory with all executables and libraries which are required for 470 this distribution. 471 </description> 472 </link> 473 </collection> 474 <link name="template"> 475 <description> 476 Symlink to the default template for this distribution. 477 </description> 478 </link> 479 </collection> 480 481 <!-- Vserver configuration --> 482 <collection name="vserver-name" type="symbolic"> 483 <description> 484 The configuration directory for the vserver vserver-name. 485 </description> 486 487 <link name="cache"> 488 <default>../.defaults/cachebase/VSERVERNAME</default> 489 <description> 490 Path of the storage area for cached information about this vserver. 491 </description> 492 </link> 493 494 <link name="vdir"> 495 <default>../.defaults/vdirbase/VSERVERNAME</default> 496 <description> 497 Path of the vserver root directory. 498 </description> 499 </link> 500 501 <link name="run"> 502 <description> 503 Points to a file which will contain the XID of the running vserver. When 504 the vserver is stopped, this can be a dangling symlink. 505 </description> 506 </link> 507 508 <list id="bcapabilities" name="bcapabilities"> 509 <description> 510 Contains the system capabilities. See 511 <ulink url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/bcaps-v13.c">lib/bcaps-v13.c</ulink> 512 for possible values. 513 </description> 514 </list> 515 <list name="ccapabilities"> 516 <description> 517 Contains the context capabilities. See <ulink 518 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/ccaps-v13.c">lib/ccaps-v13.c</ulink> 519 for possible values. 520 </description> 521 </list> 522 <list name="ncapabilities" since="0.30.212"> 523 <description> 524 Contains the network capabilities. See <ulink 525 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/ncaps-net.c">lib/ncaps-net.c</ulink> 526 for possible values. 527 </description> 528 </list> 529 <list name="umask" since="0.30.216"> 530 <description> 531 Contains the namespaces allowed to be unshared. See <ulink 532 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/umask-v23.c">lib/umask-v23.c</ulink> 533 for possible values. 534 </description> 535 </list> 536 537 <boolean id="global-namespace" name="namespace"> 538 <description> 539 Overrides the global <optionref ref="global-nonamespace">nonamespace</optionref> flag and enables 540 namespace usage for the current vserver. 541 </description> 542 </boolean> 543 544 <boolean name="nonamespace"> 545 <description> 546 Disables namespace usage for the current vserver. 547 548 In this mode the <directory>/vservers</directory> directory must have 549 the 'barrier' attribute. Else, common chroot(2) exploits are possible. 550 </description> 551 </boolean> 552 553 <boolean id="namespace-cleanup" name="namespace-cleanup"> 554 <description> 555 Overrides the global <optionref ref="global-nonamespace-cleanup">nonamespace-cleanup</optionref> flag and enables 556 namespace cleanup for the current vserver. 557 </description> 558 </boolean> 559 560 <list name="namespace-cleanup-skip"> 561 <description> 562 List of paths to skip during namespace cleanup. This overrides the global 563 <optionref ref="global-namespace-cleanup-skip">namespace-cleanup-skip</optionref> 564 file. 565 </description> 566 </list> 567 568 <hash name="schedule"> 569 <description> 570 [deprecated; use <optionref ref="sched">sched</optionref> instead] Contains the 571 scheduler parameters, one per line. 572 573 The Hard CPU limit uses a mechanism called a Token Bucket. the 574 concept is simple: you have a bucket of a certain size which is 575 filled with a specified amount R of tokens each interval T until the 576 maximum is reached (excess tokens are spilled). At each timer tick, 577 a running process consumes one token from the bucket, unless the 578 bucket is empty. If the bucket is empty the process is put in the 579 hold queue. When the bucket has been refilled to at least M tokens, 580 all on hold processes are rescheduled. 581 582 See the <ulink url="http://linux-vserver.org/Scheduler+Parameters">Linux 583 VServer Wiki</ulink> for more information about this file. 584 </description> 585 <keys> 586 <key id="fill_rate" name="fill-rate"> 587 <description> 588 Amount of tokens append to the bucket each interval. 589 </description> 590 </key> 591 <key name="interval"> 592 <description> 593 The intervall between refills of amount <optionref>fill_rate</optionref>. This 594 value is express in ticks. 595 </description> 596 </key> 597 <key name="tokens"> 598 <description> 599 Initial bucket contents. 600 </description> 601 </key> 602 <key name="tokens-min"> 603 <description> 604 The minimum amount of tokens required to unhold processes 605 </description> 606 </key> 607 <key name="tokens-max"> 608 <description> 609 The bucket size. 610 </description> 611 </key> 612 <key name="priority-bias"> 613 <description> 614 ??? 615 </description> 616 </key> 617 </keys> 618 </hash> 619 <scalar name="name"> 620 <description> 621 Contains the name of the vserver. When not given, the basename of the directory 622 will be assumed as this name. 623 </description> 624 </scalar> 625 <scalar name="nice"> 626 <description> 627 The nice-level on which the vserver will be started. 628 </description> 629 </scalar> 630 <list name="capabilities"> 631 <description> 632 Contains per line a capability. This file is used for the 2.4 kernel 633 only; for 2.6 use <optionref>bcapabilities</optionref>. 634 </description> 635 </list> 636 <scalar id="shell" name="shell"> 637 <description> 638 Contains the pathname of the shell which will be used by the "vserver 639 ... enter" command. 640 </description> 641 </scalar> 642 <list name="personality"> 643 <description> 644 Used to set the personality of the vserver. First line in the file 645 is the personality-type followed by flags (one item per line). See 646 <filename>/usr/include/linux/personality.h</filename> for possible 647 values. 648 </description> 649 </list> 650 <list name="cflags" id="cflags" since="0.30.216"> 651 <description> 652 Contains per line a flag. See <ulink 653 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/cflags-v13.c">lib/cflags-v13.c</ulink> 654 for possible values. 655 </description> 656 </list> 657 <list name="flags"> 658 <description> 659 Old name for <optionref>cflags</optionref>. Deprecated. 660 </description> 661 </list> 662 <list name="nflags" since="0.30.212"> 663 <description> 664 Contains a network flag per line. See <ulink 665 url="http://svn.linux-vserver.org/svn/util-vserver/trunk/lib/nflags-net.c">lib/nflags-net.c</ulink> 666 for possible values. 667 </description> 668 </list> 669 <scalar name="context"> 670 <description> 671 Contains the context id which shall be used for the vserver. Valid range is 2 through 49151. 672 </description> 673 </scalar> 674 <scalar name="ncontext"> 675 <description> 676 Contains the network context id which shall be used for the vserver. Valid range is 2 through 49151. 677 </description> 678 </scalar> 679 <boolean name="noncontext" since="0.30.216" id="noncontext"> 680 <description> 681 When this file exists, it disables network isolation for this guest. Typically used with netns. 682 </description> 683 </boolean> 684 <scalar name="tag"> 685 <description> 686 Contains the filesystem tag which shall be used for the vserver. Valid range is 2 through 49151. 687 </description> 688 </scalar> 689 <data id="fstab" name="fstab"> 690 <description> 691 The fstab file for the vserver. Entries in this file will be mounted 692 within the network context of the host. Use the 693 <optionref>fstab.remote</optionref> file when you want that the 694 mounting happens in the network context of the vserver. In most cases 695 the 'fstab' file should be used. 696 </description> 697 </data> 698 <data id="fstab.remote" name="fstab.remote"> 699 <description> 700 The fstab file for the vserver. Entries in this file will be mounted 701 within the network context of the guest; this means that mount will be 702 called as <command>chbind <options> mount ...</command>. See 703 <optionref>fstab</optionref> also. 704 </description> 705 </data> 706 <scalar name="badness"> 707 <description> 708 Contains the bias to be applied to processes in this guest when the OOM-killer strikes. 709 </description> 710 </scalar> 711 712 <collection name="apps"> 713 <collection name="init"> 714 <data name="mtab"> 715 <description> 716 The initial-mtab which will be used for the vserver. 717 </description> 718 </data> 719 720 <scalar name="style"> 721 <description> 722 Contains the init-style. 723 </description> 724 <restriction> 725 <enumeration value="sysv"/> 726 <enumeration value="plain"/> 727 <enumeration value="minit"/> 728 </restriction> 729 </scalar> 730 731 <scalar name="runlevel"> 732 <description>The start runlevel.</description> 733 </scalar> 734 735 <scalar name="runlevel.start"> 736 <description>The start runlevel.</description> 737 </scalar> 738 739 <scalar name="runlevel.stop"> 740 <description>The stop runlevel.</description> 741 </scalar> 742 743 <scalar name="killseq"> 744 <description> 745 Contains the 'signal [wait signal]*' sequence which is used to stop 746 the vserver. 747 </description> 748 </scalar> 749 750 <list name="cmd.start"> 751 <description> 752 The command which is used to start the vserver. Each option must be on 753 a separate line. 754 </description> 755 </list> 756 757 <list name="cmd.start-sync"> 758 <description> 759 The command which is used to wait on the vserver after it has been 760 started. Each option must be on a separate line. This file will be 761 ignored when the <optionref>sync</optionref> flag does not exist and the 762 '--sync' option was not used. 763 </description> 764 </list> 765 766 <list name="cmd.stop"> 767 <description> 768 The command which is used to stop the vserver. Each option must be on 769 a separate line. 770 </description> 771 </list> 772 773 <list name="cmd.stop-sync"> 774 <description> 775 The command which is used to wait on the vserver after it has been 776 stopped. Each option must be on a separate line. This file will be 777 ignored when the <optionref>sync</optionref> flag does not exist and the 778 '--sync' option was not used. 779 </description> 780 </list> 781 782 <list name="cmd.prepare"> 783 <description> 784 The command which is used to setup the init-system (e.g. to set the 785 runlevel in the utmp-file). Each option must be on a separate line. 786 </description> 787 </list> 788 789 <boolean id="sync" name="sync"> 790 <description> 791 If this file is not present, all 'cmd.*-sync files will be ignored. 792 </description> 793 </boolean> 794 795 <link name="tty"> 796 <description> 797 A symlink to the TTY device where input/output will be redirected 798 from/to at startup via initscript. 799 </description> 800 </link> 801 802 <scalar name="mark"> 803 <description> 804 This file is used to mark group of vservers which shall be started/stopped 805 together by the initscript. Content is a simple string like 'default'. 806 </description> 807 </scalar> 808 809 <list name="depends"> 810 <description> 811 This file is used to configure vservers which must be running before 812 the current vserver can be started. At shutdown, the current vserver 813 will be stopped before its dependencies. Content of this file are 814 vserver ids (one name per line). 815 </description> 816 </list> 817 818 <hash name="environment" since="0.30.211"> 819 <description> 820 The environment to set when starting the guest. Contains one VAR=VAL 821 pair per line. 822 </description> 823 </hash> 824 </collection> 825 826 <collection name="vdevmap"> 827 <collection name="x" type="sybmolic"> 828 <description>'x' is an arbitrary name, replace it with e.g. device names</description> 829 <boolean name="open"> 830 <description>When this file exists, the device can be opened</description> 831 </boolean> 832 <boolean name="create"> 833 <description>When this file exists, the device can be created (if the guest has <optionref ref="bcapabilities">CAP_MKNOD</optionref>)</description> 834 </boolean> 835 <boolean id="guest-vdevmap-remap" name="remap"> 836 <description> 837 When this file exists, <optionref ref="guest-vdevmap-target">target</optionref> will 838 have to exist as well and opening the device will in fact open the target device 839 </description> 840 </boolean> 841 <scalar name="flags"> 842 <description>This file will let you specify unimplemented flags manually</description> 843 </scalar> 844 <scalar name="device"> 845 <description>Contains the name of a device node</description> 846 </scalar> 847 <scalar id="guest-vdevmap-target" name="target"> 848 <description>Contains the device node of the target node to open instead of the device when <optionref ref="guest-vdevmap-remap">remap</optionref> is set</description> 849 </scalar> 850 </collection> 851 </collection> 852 853 <collection name="vshelper"> 854 <scalar name="sync-timeout"> 855 <default>30</default> 856 <description> 857 The timeout in seconds which is used when synchronising vserver 858 startup/shutdown with the vshelper. When not set, 30 seconds will be 859 assumed. 860 </description> 861 </scalar> 862 863 <scalar id="vshelper-action" name="action"> 864 <default>restart</default> 865 <description> 866 The action which is going to be executed when a vshelper event 867 occurs. The default value is 'restart', but there can be defined own 868 methods by placing scripts into the 869 <optionref>vshelper-methods</optionref> directories. These scripts are 870 fed with the same arguments as the <tool>vshelper</tool> script. 871 </description> 872 </scalar> 873 874 <program name="event" type="symbolic"> 875 <description> 876 When existing, these scripts will be executed *instead* of the default 877 handler defined in 'action'. Their name must match the event which caused 878 the execution of <tool>vshelper</tool>; e.g. 'restart' or 'poweroff'. See 879 the vs_reboot() function in the kernel for more details. 880 </description> 881 <parameterList> 882 <parameter name="xid"> 883 <description> 884 The xid of the context calling the vshelper 885 </description> 886 </parameter> 887 <parameter name="event"> 888 <description> 889 The reboot-event. 890 </description> 891 </parameter> 892 </parameterList> 893 </program> 894 895 <boolean name="disabled"> 896 <description> 897 When existing, the vshelper functionality will be disabled for this 898 vserver. 899 </description> 900 </boolean> 901 902 <boolean name="debug"> 903 <description> 904 When existing, the vshelper execution will be traced for this vserver. 905 </description> 906 </boolean> 907 908 <boolean name="warning-disabled"> 909 <description> 910 When existing, sanity checks for the vshelper functionality will be 911 skipped. 912 </description> 913 </boolean> 914 915 </collection> 916 917 <collection id="vshelper-methods" name="vshelper-methods"> 918 <program name="handler" type="symbolic"> 919 <description> 920 See <optionref ref="vshelper-action">vshelper/action</optionref>. 921 </description> 922 </program> 923 </collection> 924 925 <collection name="vunify"> 926 <description> 927 This directory contains configuration data required for vserver 928 unification. 929 </description> 930 931 <list name="exclude"> 932 <description> 933 <p>Static list of files which are excluded for unification. This list 934 supports an rsync-like syntax: when a file is prefixed by '+', it is a 935 candidate for unification; when there is no prefix or a '-' or a '~' it 936 will be excluded. Shell-wildcards are allowed for the filenames.</p> 937 <p>When used with <tool>vcopy</tool>, the '~' prefix prevents copying 938 of the file entirely (e.g. for keyfiles). With this tool, the file will 939 be copied instead of hardlinked when the '-' prefix is used.</p> 940 </description> 941 </list> 942 943 <link name="refserver.X" type="symbolic"> 944 <description> 945 These are symlinks to the configuration directory 946 (e.g. CONFDIR/vservers/<id>) of a refserver. There may be 947 multiple such symlinks but they must be prefixed by 'refserver.' and 948 will be processed in alphanumerical order. 949 </description> 950 </link> 951 952 <collection name="hash" since="0.30.205"> 953 <description> 954 A directory which will be used as the storage place for the 955 <tool>vhashify</tool> command. 956 </description> 957 <link name="id" type="symbolic"> 958 <description> 959 Points to a directory within the filesystems which are used for the 960 vservers. There must be not more than one of such a directory per 961 filesystem. 962 </description> 963 </link> 964 965 <scalar name="method" since="0.30.299"> 966 <default>SHA1</default> 967 <description>The used hash method.</description> 968 </scalar> 969 </collection> 970 971 <boolean name="pkgmgmt-ignore" default="off" since="0.30.205"> 972 <description> 973 When existing, information from packagemanagement will not be used to 974 create dynamic exclude-lists. 975 </description> 976 </boolean> 977 978 <boolean name="pgkmgmt-force" default="off" since="0.30.205"> 979 <description> 980 When existing, information from packagemanagement will be used to 981 create dynamic exclude-lists. This option requires that (a known) 982 packagemanagement is configured for the vserver; else the requested 983 operation will fail. Most tools assume 'on' as the default value. 984 </description> 985 </boolean> 986 987 </collection> 988 </collection> 989 990 <collection name="scripts"> 991 <description> 992 A directory for scripts. By default, when one of these scripts will be 993 executed, the execution of defaultscripts (within .../.defaults/scripts) 994 will be skipped. To execute them nevertheless, the $DONT_SKIP_DEFAULTS 995 environment variable must be set by one of the in-shellcontext scripts 996 (the non-executable ones). 997 </description> 998 999 <program name="initialize" since="0.30.211"> 1000 <description> 1001 The scriptlet which will be executed before the root filesystem is mounted and 1002 the configuration has been loaded. Before executing the script, the 1003 configuration directory will be made the working directory. 1004 </description> 1005 <parameterList> 1006 <parameter name="action"> 1007 <description> 1008 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1009 </description> 1010 </parameter> 1011 <parameter name="vserver-name"> 1012 <description> 1013 The name of the current vserver. 1014 </description> 1015 </parameter> 1016 </parameterList> 1017 </program> 1018 <collection name="initialize.d" since="0.30.211"> 1019 <description> 1020 Repository of initialize like scripts. Before executing the script, 1021 the configuration directory will be made the working directory. 1022 </description> 1023 <program name="script" type="symbolic"> 1024 <description>See initialize.</description> 1025 <parameterList> 1026 <parameter name="action"> 1027 <description> 1028 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1029 </description> 1030 </parameter> 1031 <parameter name="vserver-name"> 1032 <description> 1033 The name of the current vserver. 1034 </description> 1035 </parameter> 1036 </parameterList> 1037 </program> 1038 </collection> 1039 1040 <program name="prepre-start"> 1041 <description> 1042 The scriptlet which will be executed before the network-interfaces are 1043 enabled and the directories are mounted. Before executing the script, 1044 the configuration directory will be made the working directory. 1045 </description> 1046 <parameterList> 1047 <parameter name="action"> 1048 <description> 1049 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1050 </description> 1051 </parameter> 1052 <parameter name="vserver-name"> 1053 <description> 1054 The name of the current vserver. 1055 </description> 1056 </parameter> 1057 </parameterList> 1058 </program> 1059 <collection name="prepre-start.d"> 1060 <description> 1061 Repository of prepre-start like scripts. Before executing the script, 1062 the configuration directory will be made the working directory. 1063 </description> 1064 <program name="script" type="symbolic"> 1065 <description>See prepre-start.</description> 1066 <parameterList> 1067 <parameter name="action"> 1068 <description> 1069 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1070 </description> 1071 </parameter> 1072 <parameter name="vserver-name"> 1073 <description> 1074 The name of the current vserver. 1075 </description> 1076 </parameter> 1077 </parameterList> 1078 </program> 1079 </collection> 1080 1081 <program name="pre-start"> 1082 <description> 1083 The scriptlet which will be executed after network-interfaces were 1084 enabled and the directories mounted, but before the vserver itself has 1085 been started. Before executing the script, the vserver root directory 1086 will be made the working directory. 1087 </description> 1088 <parameterList> 1089 <parameter name="action"> 1090 <description> 1091 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1092 </description> 1093 </parameter> 1094 <parameter name="vserver-name"> 1095 <description> 1096 The name of the current vserver. 1097 </description> 1098 </parameter> 1099 </parameterList> 1100 </program> 1101 <collection name="pre-start.d"> 1102 <description> 1103 Repository of pre-start like scripts. Before executing these scripts, 1104 the vserver root directory will be made the working directory. 1105 </description> 1106 <program name="script" type="symbolic"> 1107 <description>See pre-start.</description> 1108 <parameterList> 1109 <parameter name="action"> 1110 <description> 1111 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1112 </description> 1113 </parameter> 1114 <parameter name="vserver-name"> 1115 <description> 1116 The name of the current vserver. 1117 </description> 1118 </parameter> 1119 </parameterList> 1120 </program> 1121 </collection> 1122 1123 1124 <program name="post-start"> 1125 <description> 1126 The scriptlet which will be executed after the vserver has been 1127 started. Before executing the script, the vserver root directory 1128 will be made the working directory. 1129 </description> 1130 <parameterList> 1131 <parameter name="action"> 1132 <description> 1133 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1134 </description> 1135 </parameter> 1136 <parameter name="vserver-name"> 1137 <description> 1138 The name of the current vserver. 1139 </description> 1140 </parameter> 1141 </parameterList> 1142 </program> 1143 <collection name="post-start.d"> 1144 <description> 1145 Repository of post-start like scripts. Before executing these scripts, 1146 the vserver root directory will be made the working directory. 1147 </description> 1148 <program name="script" type="symbolic"> 1149 <description>See post-start.</description> 1150 <parameterList> 1151 <parameter name="action"> 1152 <description> 1153 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1154 </description> 1155 </parameter> 1156 <parameter name="vserver-name"> 1157 <description> 1158 The name of the current vserver. 1159 </description> 1160 </parameter> 1161 </parameterList> 1162 </program> 1163 </collection> 1164 1165 1166 <program name="pre-stop"> 1167 <description> 1168 The scriptlet which will be executed before the vserver will be 1169 stopped. Before executing the script, the vserver root directory 1170 will be made the working directory. 1171 </description> 1172 <parameterList> 1173 <parameter name="action"> 1174 <description> 1175 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1176 </description> 1177 </parameter> 1178 <parameter name="vserver-name"> 1179 <description> 1180 The name of the current vserver. 1181 </description> 1182 </parameter> 1183 </parameterList> 1184 </program> 1185 <collection name="pre-stop.d"> 1186 <description> 1187 Repository of pre-stop like scripts. Before executing the script, the 1188 vserver root directory will be made the working directory. 1189 </description> 1190 <program name="script" type="symbolic"> 1191 <description>See pre-stop.</description> 1192 <parameterList> 1193 <parameter name="action"> 1194 <description> 1195 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1196 </description> 1197 </parameter> 1198 <parameter name="vserver-name"> 1199 <description> 1200 The name of the current vserver. 1201 </description> 1202 </parameter> 1203 </parameterList> 1204 </program> 1205 </collection> 1206 1207 <program name="post-stop"> 1208 <description> 1209 The scriptlet which will be executed after the vserver has been 1210 stopped, but before the directories will be umounted and the the 1211 interfaces disabled. Before executing the script, the vserver root 1212 directory will be made the working directory. 1213 </description> 1214 <parameterList> 1215 <parameter name="action"> 1216 <description> 1217 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1218 </description> 1219 </parameter> 1220 <parameter name="vserver-name"> 1221 <description> 1222 The name of the current vserver. 1223 </description> 1224 </parameter> 1225 </parameterList> 1226 </program> 1227 <collection name="post-stop.d"> 1228 <description> 1229 Repository of post-stop like scripts. Before executing the script, the 1230 vserver root directory will be made the working directory. 1231 </description> 1232 <program name="script" type="symbolic"> 1233 <description>See post-stop.</description> 1234 <parameterList> 1235 <parameter name="action"> 1236 <description> 1237 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1238 </description> 1239 </parameter> 1240 <parameter name="vserver-name"> 1241 <description> 1242 The name of the current vserver. 1243 </description> 1244 </parameter> 1245 </parameterList> 1246 </program> 1247 </collection> 1248 1249 <program name="postpost-stop"> 1250 <description> 1251 The scriptlet which will be executed after the vserver has been stopped 1252 completely. Before executing the script, the vserver root directory 1253 will be made the working directory. 1254 </description> 1255 <parameterList> 1256 <parameter name="action"> 1257 <description> 1258 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1259 </description> 1260 </parameter> 1261 <parameter name="vserver-name"> 1262 <description> 1263 The name of the current vserver. 1264 </description> 1265 </parameter> 1266 </parameterList> 1267 </program> 1268 <collection name="postpost-stop.d"> 1269 <description> 1270 Repository of postpost-stop like scripts. Before executing the script, 1271 the vserver root directory will be made the working directory. 1272 </description> 1273 <program name="script" type="symbolic"> 1274 <description>See postpost-stop.</description> 1275 <parameterList> 1276 <parameter name="action"> 1277 <description> 1278 The fixed value of the current action (e.g. 'prepre-start', 'post-stop'...). 1279 </description> 1280 </parameter> 1281 <parameter name="vserver-name"> 1282 <description> 1283 The name of the current vserver. 1284 </description> 1285 </parameter> 1286 </parameterList> 1287 </program> 1288 </collection> 1289 </collection> 1290 1291 <collection name="interfaces"> 1292 <scalar name="bcast"> 1293 <description>The guest's broadcast address.</description> 1294 </scalar> 1295 <scalar name="lback"> 1296 <description>The guest's loopback address.</description> 1297 </scalar> 1298 <scalar name="dev"> 1299 <description>The default network device. See <optionref ref="per-if-dev">iface/dev</optionref> for more information.</description> 1300 </scalar> 1301 <scalar name="prefix"> 1302 <description>The default network prefix-length.</description> 1303 </scalar> 1304 <scalar name="mask"> 1305 <description>The default network mask.</description> 1306 </scalar> 1307 <scalar name="scope"> 1308 <description>The default scope of the network interfaces.</description> 1309 </scalar> 1310 <boolean id="local-vlandev" name="vlandev" since="0.30.211"> 1311 <description> 1312 When this file exists, the steps which setup and destroy a VLAN 1313 interface will be executed for all interfaces of this vserver. 1314 </description> 1315 </boolean> 1316 <boolean id="local-novlandev" name="novlandev"> 1317 <description> 1318 When this file exists, the steps which setup and destroy a VLAN 1319 interface will be skipped. This overrides the global 1320 <optionref ref="global-vlandev">vlandev</optionref> setting for 1321 this vserver. 1322 </description> 1323 </boolean> 1324 1325 <collection name="iface" type="symbolic"> 1326 <description> 1327 'iface' is an arbitrary name for the interface; the value itself is 1328 not important but may be interesting regarding interface-creation and 1329 usage with <tool>chbind</tool>. Both happens in alphabetical order and 1330 numbers like '00' are good names for these directories. 1331 </description> 1332 1333 <boolean name="disabled"> 1334 <description>When this file exists, this interface will be ignored.</description> 1335 </boolean> 1336 1337 <scalar name="ip"> 1338 <description>The IP address which will be assigned to this interface.</description> 1339 </scalar> 1340 <scalar name="dev" id="per-if-dev"> 1341 <description>The network device. When this is specified, the IP address will be assigned and removed when starting and stopping the guest.</description> 1342 </scalar> 1343 <scalar name="prefix"> 1344 <description>The network prefix-length.</description> 1345 </scalar> 1346 <scalar name="mask"> 1347 <description>The network mask.</description> 1348 </scalar> 1349 <scalar name="scope"> 1350 <description>The scope of the network interface.</description> 1351 </scalar> 1352 <scalar name="name"> 1353 <description> 1354 When this file exists, the interface will be named with the text in 1355 this file. Without such an entry, the IP will not be shown by 1356 <tool>ifconfig</tool> but by <command>ip addr ls</command> only. Such 1357 a labeled interface is known as an "alias" also (e.g. 'eth0:foo'). 1358 </description> 1359 </scalar> 1360 <boolean name="nodev"> 1361 <description> 1362 When this file exists, the interface will be assumed to exist 1363 already. This can be used to assign primary interfaces which are 1364 created by the host or another vserver. 1365 </description> 1366 </boolean> 1367 <boolean name="novlandev"> 1368 <description> 1369 When this file exists, the steps which setup and destroy a VLAN 1370 interface will be skipped. This will override the global 1371 <optionref ref="global-vlandev">vlandev</optionref> and the per-guest 1372 <optionref ref="local-vlandev">vlandev</optionref>. 1373 </description> 1374 </boolean> 1375 <boolean name="vlandev" since="0.30.211"> 1376 <description> 1377 When this file exists, the steps which setup and destroy a VLAN 1378 interface will be executed. 1379 </description> 1380 </boolean> 1381 <boolean name="tun" since="0.30.215"> 1382 <description> 1383 When this file exists, a tun interface will be created when the guest 1384 starts, and removed when the guest stops. 1385 </description> 1386 </boolean> 1387 <boolean name="tap" since="0.30.215"> 1388 <description> 1389 When this file exists, a tap interface will be created when the guest 1390 starts, and removed when the guest stops. 1391 </description> 1392 </boolean> 1393 <boolean name="nocsum" since="0.30.215"> 1394 <description> 1395 If a tun or tap interface is created, the presence of this file will 1396 disable checksumming on it. 1397 </description> 1398 </boolean> 1399 <boolean name="shared" since="0.30.215"> 1400 <description> 1401 When this file exists, the tun/tap interface created will not be 1402 owned by this particular guest. 1403 </description> 1404 </boolean> 1405 <scalar name="uid" since="0.30.215"> 1406 <description> 1407 Sets the ownership of tun/tap interfaces. Requires a user id, not a 1408 username. 1409 </description> 1410 </scalar> 1411 <scalar name="gid" since="0.30.215"> 1412 <description> 1413 Sets the group ownership of tun/tap interfaces. Requires a group id, 1414 not a group name. 1415 </description> 1416 </scalar> 1417 <scalar name="linktype" since="0.30.215"> 1418 <description> 1419 Sets the link type of tun/tap interfaces. 1420 </description> 1421 </scalar> 1422 <scalar name="peer" since="0.30.216"> 1423 <description> 1424 Sets the peer for a point-to-point link, such as a tun interface. 1425 </description> 1426 </scalar> 1427 </collection> 1428 </collection> 1429 1430 <collection name="ulimits"> 1431 <description> 1432 A directory with ulimits. Possible resources are cpu, data, fsize, 1433 locks, memlock, nofile, nproc, rss and/or stack. 1434 </description> 1435 <scalar name="resource" type="symbolic"> 1436 <description> 1437 A file which contains the hard- and soft-limit of the given resource 1438 in the first line. The special keyword 'inf' is recognized. 1439 </description> 1440 </scalar> 1441 <scalar name="resource.hard" type="symbolic"> 1442 <description> 1443 A file which contains the hard-limit of the given resource in the first 1444 line. The special keyword 'inf' is recognized. 1445 </description> 1446 </scalar> 1447 <scalar name="resource.soft" type="symbolic"> 1448 <description> 1449 A file which contains the soft-limit of the given resource in the first 1450 line. The special keyword 'inf' is recognized. 1451 </description> 1452 </scalar> 1453 </collection> 1454 1455 <collection name="rlimits"> 1456 <description> 1457 A directory with resource limits. Possible resources are cpu, fsize, 1458 data, stack, core, rss, nproc, nofile, memlock, as, locks, msgqueue, 1459 nsock, openfd, anon, shmem, semary, nsems and dentry. This 1460 configuration will be honored for kernel 2.6 only. 1461 </description> 1462 <scalar name="resource" type="symbolic"> 1463 <description> 1464 A file which contains the hard- and soft-limit of the given resource 1465 in the first line. The special keyword 'inf' is recognized. 1466 </description> 1467 </scalar> 1468 <scalar name="resource.hard" type="symbolic"> 1469 <description> 1470 A file which contains the hard-limit of the given resource in the first 1471 line. The special keyword 'inf' is recognized. 1472 </description> 1473 </scalar> 1474 <scalar name="resource.soft" type="symbolic"> 1475 <description> 1476 A file which contains the soft-limit of the given resource in the first 1477 line. The special keyword 'inf' is recognized. 1478 </description> 1479 </scalar> 1480 <scalar name="resource.min" type="symbolic"> 1481 <description> 1482 A file which contains the guaranteed minimum of the given resource in 1483 the first line. The special keyword 'inf' is recognized. 1484 </description> 1485 </scalar> 1486 </collection> 1487 1488 <collection name="uts"> 1489 <scalar name="context"> 1490 <description> 1491 The context-name of the vserver. This file is listed for completeness 1492 only; the 'context' name is used and set internally by the util-vserver 1493 tools and can *not* be modified. 1494 </description> 1495 </scalar> 1496 <scalar name="sysname"> 1497 <description>The sysname of the vserver</description> 1498 </scalar> 1499 <scalar name="nodename"> 1500 <description>The node-/hostname of the vserver</description> 1501 </scalar> 1502 <scalar name="release"> 1503 <description>The OS-release of the vserver</description> 1504 </scalar> 1505 <scalar name="version"> 1506 <description>The OS-version of the vserver</description> 1507 </scalar> 1508 <scalar name="machine"> 1509 <description>The machine-type of the vserver</description> 1510 </scalar> 1511 <scalar name="domainname"> 1512 <description>The NIS domainname of the vserver</description> 1513 </scalar> 1514 </collection> 1515 1516 <collection name="dlimits" since="0.30.210"> 1517 <description> 1518 Note that all entries are required for the disk limit to be applied. 1519 </description> 1520 <collection name="x" type="symbolic"> 1521 <description>'x' is an arbitrary name, replace it with e.g. integers</description> 1522 <scalar name="directory"> 1523 <description>The directory to which the limit should be applied</description> 1524 </scalar> 1525 <scalar name="inodes_total"> 1526 <description>The amount of inodes this vserver should be limited to</description> 1527 </scalar> 1528 <scalar name="space_total"> 1529 <description>The amount of space this vserver should be limited to (measured in blocks of 1024 bytes)</description> 1530 </scalar> 1531 <scalar name="reserved"> 1532 <description>How much space (percentage-wise) should be reserved for the root user</description> 1533 </scalar> 1534 </collection> 1535 </collection> 1536 1537 <collection name="sysctl" since="0.30.213"> 1538 <collection name="x" type="symbolic"> 1539 <description>'x' is an arbitrary name, replace it with e.g. integers</description> 1540 <scalar name="setting"> 1541 <description>The sysctl setting</description> 1542 </scalar> 1543 <scalar name="value"> 1544 <description>The value</description> 1545 </scalar> 1546 </collection> 1547 </collection> 1548 1549 <collection name="cpuset" since="0.30.211"> 1550 <description> 1551 Puts the guest in a cpuset. Required entries are name, cpus and mems. 1552 </description> 1553 <scalar name="name"> 1554 <description>The name of the cpuset for this vserver</description> 1555 </scalar> 1556 <scalar name="cpus"> 1557 <description>The list of CPUs in this cpuset</description> 1558 </scalar> 1559 <scalar name="mems"> 1560 <description>The list of Memory Nodes in this cpuset</description> 1561 </scalar> 1562 <scalar name="cpu_exclusive"> 1563 <description>Is the CPU assignment exclusive?</description> 1564 </scalar> 1565 <scalar name="mems_exclusive"> 1566 <description>Is the memory node assignment exclusive?</description> 1567 </scalar> 1568 <scalar name="nocreate"> 1569 <description>When this file exists, the cpuset will be assumed to exist already</description> 1570 </scalar> 1571 </collection> 1572 1573 <collection id="sched" name="sched" since="0.30.212"> 1574 <scalar id="global-tokens" name="tokens"> 1575 <description>The initial amount of tokens to put in the bucket</description> 1576 </scalar> 1577 <scalar id="global-tokens-min" name="tokens-min"> 1578 <description>The minimum amount of tokens required to unhold the context</description> 1579 </scalar> 1580 <scalar id="global-tokens-max" name="tokens-max"> 1581 <description>The bucket's size</description> 1582 </scalar> 1583 <scalar id="global-fill-rate" name="fill-rate"> 1584 <description>Amount of tokens to add each <optionref ref="global-interval">interval</optionref></description> 1585 </scalar> 1586 <scalar id="global-interval" name="interval"> 1587 <description>The interval between refills of the bucket</description> 1588 </scalar> 1589 <scalar id="global-priority-bias" name="priority-bias"> 1590 <description>Bias added to priorities calculated within the guest (result is clamped to -20/+19)</description> 1591 </scalar> 1592 <scalar id="global-fill-rate2" name="fill-rate2"> 1593 <description>Amount of tokens to add each <optionref ref="global-interval2">interval2</optionref> when advancing idle time</description> 1594 </scalar> 1595 <scalar id="global-interval2" name="interval2"> 1596 <description>The interval between refills of the bucket when advancing idle time</description> 1597 </scalar> 1598 <boolean id="global-idle-time" name="idle-time"> 1599 <description>When this file exists, advancing idle time is activated</description> 1600 </boolean> 1601 <collection name="cpu-id" type="symbolic"> 1602 <description>This directory contains per-CPU and/or per-bucket specific settings. Remember to set the <optionref ref="cpu-id">cpu-id</optionref> file. All CPUs inherit the global settings.</description> 1603 <scalar name="tokens"> 1604 <description>The initial amount of tokens to put in the bucket</description> 1605 </scalar> 1606 <scalar name="tokens-min"> 1607 <description>The minimum amount of tokens required to unhold the context</description> 1608 </scalar> 1609 <scalar name="tokens-max"> 1610 <description>The bucket's size</description> 1611 </scalar> 1612 <scalar name="fill-rate"> 1613 <description>Amount of tokens to add each <optionref ref="local-interval">interval</optionref></description> 1614 </scalar> 1615 <scalar id="local-interval" name="interval"> 1616 <description>The interval between refills of the bucket</description> 1617 </scalar> 1618 <scalar name="priority-bias"> 1619 <description>Bias added to priorities calculated within the guest (result is clamped to -20/+19)</description> 1620 </scalar> 1621 <scalar name="fill-rate2"> 1622 <description>Amount of tokens to add each <optionref ref="local-interval2">interval2</optionref> when advancing idle time</description> 1623 </scalar> 1624 <scalar id="local-interval2" name="interval2"> 1625 <description>The interval between refills of the bucket when advancing idle time</description> 1626 </scalar> 1627 <boolean name="idle-time"> 1628 <description>When this file exists, advancing idle time is activated</description> 1629 </boolean> 1630 <scalar id="cpu-id" name="cpu-id"> 1631 <description>The CPU to apply these settings to</description> 1632 </scalar> 1633 <scalar name="bucket-id"> 1634 <description>The bucket to apply these settings to</description> 1635 </scalar> 1636 </collection> 1637 </collection> 1638 1639 <collection name="spaces" since="0.30.215"> 1640 <boolean name="pid"> 1641 <description>Enables pid virtualization for this guest</description> 1642 </boolean> 1643 <boolean name="net"> 1644 <description>Enable network virtualization for this guest</description> 1645 </boolean> 1646 <scalar name="mask"> 1647 <description>Contains a mask of spaces to clone/enter</description> 1648 </scalar> 1649 </collection> 1650 1651 <collection name="ionice" since="0.30.216"> 1652 <scalar name="class"> 1653 <description>The IO scheduling class to use for this guest (see ionice(1)).</description> 1654 </scalar> 1655 <scalar name="priority"> 1656 <description>The IO scheduling priority to use for this guest (see ionice(1)).</description> 1657 </scalar> 1658 </collection> 1659 1660 <collection name="cgroup" use="optional" since="0.30.216" id="guest-cgroup"> 1661 <description> 1662 This directory contains cgroup settings to be applied to this guest. 1663 See your kernel documentation for what settings are valid with your 1664 configuration. 1665 </description> 1666 <scalar name="name"> 1667 <description> 1668 If this file exists, the guest will be put in a cgroup named after the 1669 contents of this file. The default is to name the cgroup the same thing as the 1670 guest, unless 1671 <optionref ref="global-cgroup-name">.defaults/cgroup/name</optionref> says 1672 otherwise. 1673 </description> 1674 </scalar> 1675 </collection> 1676 <scalar name="nocgroup" since="0.30.216"> 1677 <description> 1678 If this file exists, 1679 <optionref ref="global-cgroup">.defaults/cgroup</optionref> will be ignored 1680 for this guest. 1681 </description> 1682 </scalar> 1683 1684 <collection name="netns" use="optional" since="0.30.216" id="guest-netns"> 1685 <description> 1686 When this directory exists, a network namespace will be used for this guest. 1687 Note that you typically will want to <optionref ref="noncontext">disable 1688 network isolation</optionref> when using network namespaces. 1689 </description> 1690 <scalar name="name"> 1691 <description> 1692 The name of the network namespace to use for the guest. Defaults to the 1693 guest's name. 1694 </description> 1695 </scalar> 1696 <boolean name="shared"> 1697 <description> 1698 Whether or not util-vserver should add and delete the network namespace when 1699 the guest is started and stopped, respectively. 1700 </description> 1701 </boolean> 1702 <collection name="interfaces"> 1703 <collection name="iface" type="symbolic"> 1704 <description> 1705 'iface' is an arbitrary name for the interface; the value itself is 1706 not important but may be interesting regarding interface-creation. 1707 It happens in alphabetical order and numbers like '00' are good names for 1708 these directories. 1709 1710 For each of these directories, a pair of network interfaces will be created, 1711 one left on the host, and the other moved into the guest's namespace. 1712 </description> 1713 <scalar name="host"> 1714 <description> 1715 Name of the interface on the host. 1716 </description> 1717 </scalar> 1718 <scalar name="guest"> 1719 <description> 1720 Name of the interface in the guest. Defaults to gethX, where X starts at 0 1721 and increases for every interface. 1722 </description> 1723 </scalar> 1724 <scalar name="type"> 1725 <description> 1726 Type of link to create. Defaults to veth. 1727 </description> 1728 </scalar> 1729 </collection> 1730 </collection> 1731 </collection> 1732 <scalar name="nonetns" since="0.30.216"> 1733 <description> 1734 If this file exists, 1735 <optionref ref="global-netns">.defaults/netns</optionref> will be ignored 1736 for this guest. 1737 </description> 1738 </scalar> 1739 </collection> 1740 </database>