PLDWWW: Docs/Vserver

[glen]

Author: glen   Date: Wed Nov 12 18:53:30 2008 GMT
Module: PLDWWW   URL: http://www.pld-linux.org/Docs/Vserver?action=diff&rev2=131&rev1=130
---- Log message:
typo

---- Page affected: Docs/Vserver

---- Diffs:

================================================================
The comment on the change is:
typo

  
  {{{/etc/vservers/<vserver-name>/interfaces/<iface>}}}
  
- 'iface' is an arbitrary name for the interface; the value itself is not important but may be interesting regarding interface-creation and usage with chbind. Both happens in alphabetical order and numbers like '00' are good names for these directories. 
+ 'iface' is an arbitrary name for the interface; the value itself is not important but may be interesting regarding interface-creation and usage with chbind. Both happens in alphabetical order and numbers like '00' are good names for these directories.
  
   * {{{bcast}}} The broadcast address.
   * {{{dev}}} The network device.
   * {{{disabled}}} When this file exists, this interface will be ignored.
   * {{{ip}}} The ip which will be assigned to this interface.
   * {{{mask}}} The network mask.
-  * {{{name}}} When this file exists, the interface will be named with the text in this file. Without such an entry, the IP will not be shown by ifconfig but by ip addr ls only. Such a labeled interface is known as an "alias" also (e.g. 'eth0:foo'). 
+  * {{{name}}} When this file exists, the interface will be named with the text in this file. Without such an entry, the IP will not be shown by ifconfig but by ip addr ls only. Such a labeled interface is known as an "alias" also (e.g. 'eth0:foo').
   * {{{nodev}}} When this file exists, the interface will be assumed to exist already. This can be used to assign primary interfaces which are created by the host or another vserver.
   * {{{prefix}}} The network prefix-length.
   * {{{scope}}} The scope of the network interface.
@@ -160, +160 @@

  You should decide for either package management policy:
  
  Benefits managing packages ''externally'':
-  * provides extra security 
+  * provides extra security
   * avoids duplicating RPM database and installed libraries/packages
  
  Benefits of managing packages ''internally'':
@@ -206, +206 @@

  
  From now on, the packages are managed by the vserver itself and the host system's tools should no longer be used to install or remove any packages.
  
- See this doc for further info: 
+ See this doc for further info:
  {{{
  $ less /usr/share/doc/util-vserver-build-0.30.210/package-management.txt.gz
  }}}
@@ -365, +365 @@

  
  bind requires some special device nodes inside it's chroot jail located in ''/var/lib/named''. Vserver security does not allow device node creation so you will have to install the package specifying {{{--excludepath=/var/lib/named/dev}}} and then create devices {{{/dev/null}}} and {{{/dev/random}}} from outside of the vserver context.
  
- UPDATE: vpoldek doesn't allow the {{{--excludepath}} option:
+ UPDATE: vpoldek doesn't allow the {{{--excludepath}}} option:
  
  {{{
  poldek: unrecognized option `--excludepath=/var/lib/named/dev'
@@ -518, +518 @@

  Sometimes it may happen that you need to be sure that one of the vservers is started before the others - e.g. it provides some service that other depend on. Vserver provides an easy way to do this - let's assume that ''test2'' vserver depends on ''test'' and ''foo'' vservers:
  
  {{{
- # echo test >> /etc/vservers/test2/apps/init/depends 
+ # echo test >> /etc/vservers/test2/apps/init/depends
  # echo foo >> /etc/vservers/test2/apps/init/depends
  }}}
  
@@ -949, +949 @@

   * load the {{{vroot}}} module and add it to your {{{/etc/modules}}}
     * you can optionaly increase max vroot number of devices by putting the limit in your {{{/etc/modprobe.conf}}}:
     {{{
- options vroot max_vroot=64 >> 
+ options vroot max_vroot=64 >>
  }}}
   * assing a free vroot node for the device in question:
   {{{