http://linux-vserver.org/api.php?action=feedcontributions&user=80.160.159.106&feedformat=atomLinux-VServer - User contributions [en]2024-03-29T05:52:30ZUser contributionsMediaWiki 1.20.2http://linux-vserver.org/Problematic_ProgramsProblematic Programs2007-02-26T13:08:56Z<p>80.160.159.106: fixed case</p>
<hr />
<div>Some programs do things that might work on a normal host but not inside a V-Server. This is often not a fault of V-Server itself, the programs are doing automagic things which fail and no proper error handling is done. Also sometimes the actions need special rights which are not permitted by default in V-Servers. Allowing CAPs is often not necessary since those special CAPs are only required once (e.g. when the program initializes the directories/settings/whatever).<br />
<br />
<br />
=== OpenGroupware Apache Module ===<br />
If your V-Server doesn't have access to localhost, then the connection to the OpenGroupware server will fail with a "Internal Server Error". The apache module for OpenGroupware called mod_ngobjweb uses a hardcoded "127.0.0.1" IP address in the source (handler.c line 339), this line you need to change to the IP address that should be used (the IP of the V-Server that runs the OpenGroupware? server)<br />
<br />
=== Hylafax (with CAPI) ===<br />
If you want to run hylafax in a V-Server, you will get a CAP and device problem which can be easily solved. First you need your capi20 devices in your V-Server, which can't be created by ./MAKEDEV (requires special CAPs) so copy the devices into the V-Server, like this (command run on the host):<pre>cp -aR /dev/capi* /vservers/your_vserver/dev</pre><br />
<br />
Now hylafax can access your CAPI ISDN card but will exit after a few seconds, the problem is it tries to create a /dev/null nod in the hylafax chroot. This fails because of missing CAPs, so lets help hylafax again with copying the nod into the hylafax chroot in the V-Server. Like this (command run on the host):<pre>cp -aR /dev/null /vservers/your_vserver/var/spool/hylafax/dev</pre> <br />
Allright, now hylafax should have CAPI access and run properly.<br />
<br />
=== Links inside screen inside a V-Server ===<br />
Don't know why, but links crashes systematically being inside a screen session inside a V-Server started outside a V-Server. (please elaborate!) <br />
<br />
=== screen inside a VServer ===<br />
<br />
<pre>[root@ge root]# vserver zoe enter<br />
<br />
zoe:/# screen<br />
Cannot open your terminal '/dev/pts/5' - please check.<br />
<br />
zoe:/# strace screen <br />
...<br />
stat64("/dev/pts/5", {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0<br />
open("/dev/pts/5", O_RDWR|O_NONBLOCK) = -1 EACCES (Permission denied)</pre><br />
<br />
is neither a bug nor an issue with screen, it just shows that a vserver context is not allowed to mess with host terminals. either use ssh/telnet to reach the 'guest' or start the screen session before you do the 'enter' (i.e. on the host)<br />
<br />
=== OpenLDAP Startup ===<br />
slapd needs name resolution available in order to start up, otherwise it appears to hang. Make sure you have working DNS (or whatever) available to your vserver before starting one with slapd. This behavior is confirmed in my setup, no confirmation from others yet. My Setup: vservers all bind to an interface on a DMZ-like network segment, BIND runs on a vserver. slapd would hang at startup if the BIND vserver had not been started first. <br />
<br />
=== rndc ===<br />
Bind's rndc has a hardcoded 127.0.0.1 somewhere so any command to rndc will fail with connection refused. You should have a reachable localhost address defined in /etc/hosts and then you can use <pre>rndc -s localhost</pre> command. You can make a rndc.conf and set the default-server option, like that the '-s localhost' isn't necessary. <br />
<br />
=== Asterisk ===<br />
Since some version of Asterisk (at least since 1.0.2), it will not run anymore. On start it fails with: "Unable to set high priority". <br />
This can be solved by allowing CAP_SYS_NICE for that V-Server. You can also not run Asterisk with the realtime priority - Just pass the '-p' command ligne argument to disable the read-time priority. Good doc on setting up Asterisk devices in the vserver: http://www.telephreak.org/papers/vpa/<br />
<br />
=== Open/FreeSwan ===<br />
Fails because of writing to /proc (requires patch) TODO: write me <br />
<br />
=== Samba ===<br />
Oplocks don't work as smbd insists on receiving break requests from 127.0.0.1<br />
Just patch source/smbd/oplock.c (commenting paranoid code)<br />
<pre><br />
+++ oplock.c.orig 2005-02-14 14:27:51.000000000 +0200<br />
--- oplock.c 2005-02-02 12:27:50.000000000 +0200<br />
@@ -181,14 +181,12 @@<br />
return False;<br />
}<br />
<br />
+#if 0<br />
/* Validate message from address (must be localhost). */<br />
if(from.sin_addr.s_addr != htonl(INADDR_LOOPBACK)) {<br />
DEBUG(0,("receive_local_message: invalid 'from' address \<br />
(was %lx should be 127.0.0.1)\n", (long)from.sin_addr.s_addr));<br />
return False;<br />
}<br />
+#endif<br />
<br />
/* Setup the message header */<br />
SIVAL(buffer,OPBRK_CMD_LEN_OFFSET,msg_len);<br />
</pre><br />
or if you don't want to patch the samba source code you can disable oplock in Samba and it will work too!<br />
<br />
Just put the following in your smb.conf:<br />
<pre><br />
kernel oplocks = no<br />
oplocks = no<br />
</pre><br />
Note: The Vserver using Samba should also listen on the broadcast address. Thereby you will not be able to have two samba servers in the same net (on the same broadcast).<br />
<br />
==== Samba from Debian 3.1 ====<br />
<br />
The samba deb in sarge (3.1) provided file sharing. The only oddity observed is that the vserver guest running samba did not appear in a windows box's 'My Network Places'<br />
<br />
Use a WINS server. The SMB browsing protocol relies heavily on broadcasts on the local net, which are problematic with vservers. WINS resolution on the other hand is unicast and works flawlessly under vserver.<br />
<br />
==== Samba printer and file server with cups ====<br />
Samba runs correctly in a Mandriva (Mdk) 10.1 Vserver, (Apart from the above oplock problem ?).First, edit your ''/etc/sysconfig/network'' file, and set ''networking'' to ''yes'' (This will solve problems for other services !):<br />
<pre><br />
# cat /etc/sysconfig/network<br />
NETWORKING=yes<br />
</pre><br />
Some more tweaking is needeed in ''/etc/smb.conf''<br />
<pre><br />
# cat /etc/smb.conf<br />
...<br />
# YOUR VSERVER IP/MASK HERE<br />
interfaces = xxx.xxx.xxx.xxx/mask<br />
...<br />
</pre><br />
<br />
But if you're using Samba + Cups to provide printing for Windows clients, AND if you want to use the ''Point and Print'' feature, there is more: In the ''[printers]'' section of your ''smb.conf'', you should have the ''use client drivers'' directive set to ''no'', or the driver upload procedure will fail !<br />
<pre><br />
# cat /etc/smb.conf<br />
...<br />
use client driver = no<br />
...<br />
</pre><br />
So, here is a full ''smb.conf'' file: <br />
<pre><br />
# cat /etc/samba/smb.conf | awk '!/^$/ && !/^\s*(#|;)/ {print $0}'<br />
[global]<br />
workgroup = MYDOMAIN<br />
netbios name = MYHOSTNAME<br />
server string = MYCOMMENT (Samba %v)<br />
printcap name = cups<br />
load printers = yes<br />
printing = cups<br />
printer admin = @adm<br />
log file = /var/log/samba/log.%m<br />
max log size = 50<br />
map to guest = bad user<br />
security = domain<br />
password server = *<br />
encrypt passwords = yes<br />
smb passwd file = /etc/samba/smbpasswd<br />
username map = /etc/samba/smbusers<br />
idmap uid = 10000-20000<br />
idmap gid = 10000-20000<br />
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192<br />
interfaces = 127. MYVSERVERIP/MYVSERVERMASK<br />
wins server = MYWINSIP<br />
dns proxy = no<br />
# for french users:<br />
dos charset = 850<br />
unix charset = ISO8859-1<br />
[homes]<br />
comment = Home Directories<br />
browseable = no<br />
writable = no<br />
[printers]<br />
comment = All Printers<br />
path = /var/spool/samba<br />
browseable = no<br />
guest ok = no<br />
writable = no<br />
printable = yes<br />
create mode = 0700<br />
print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers.<br />
use client driver = no<br />
[print$]<br />
path = /var/lib/samba/printers<br />
browseable = yes<br />
write list = @adm root<br />
guest ok = yes<br />
inherit permissions = yes<br />
</pre><br />
...And a working smbusers:<br />
<pre><br />
# Unix_name = SMB_name1 SMB_name2 ...<br />
root = administrator MYDOMAIN\administrator<br />
nobody = guest pcguest smbguest<br />
</pre><br />
<br />
=== Cups print server ===<br />
Symptoms: The Cups init script exits with:<br />
<pre><br />
Starting CUPS printing system: cupsd: Child exited with status 98!<br />
</pre> <br />
And the logs (''/var/log/cups/error_log'') show:<br />
<pre> <br />
E [date:hour...] StartListening: Unable to bind socket for address 0.0.0.0:631 - Address already in use.<br />
</pre> <br />
...Or something like this. <br />
<br />
With a correct "cupsd.conf file" (Tested version 1.1.21-0.rc1.7mdk, on Mandrake 10.1 - Now Mandriva), it works; All we need is to remove references to ''127.0.0.1'' or ''localhost'' from the file, as well as correctly unsetting the ''Listen'' directive:<br />
<pre> <br />
LogLevel info<br />
TempDir /var/spool/cups/tmp<br />
# No 'Listen' directive !<br />
Port 631<br />
BrowseAddress @LOCAL<br />
BrowseDeny All<br />
BrowseAllow @LOCAL<br />
BrowseOrder deny,allow<br />
<Location /><br />
Order Deny,Allow<br />
Deny From All<br />
Allow From @LOCAL<br />
</Location><br />
<Location /admin><br />
AuthType Basic<br />
AuthClass System<br />
Order Deny,Allow<br />
Deny From All<br />
Allow From YOUR_NETWORK_ADDRESS/YOUR_NETMASK # Example: 172.16.0.0/24<br />
# Or<br />
Allow From @LOCAL<br />
</Location><br />
</pre> <br />
Then you'll need to modify the ''/etc/init.d/cups'' script, to comment any section referring to ''127.0.0.1'' lookup and configuration. This section exists at least on Mandrake 10.1, and is pretty long (Lines 35 to 55 and/or 79), and additionnaly four "''else...if''" lines must be commented far below (Lines 161 to 164) ! <br />
<br />
Remember to stop any Cupsd running in the host server, or to start it via a wrapper ''/etc/init.d/v_cups'' script: <br />
<pre> <br />
#!/bin/sh<br />
# chkconfig: 2345 15 60<br />
# description: Wrapper to start cups bound to a single IP<br />
USR_LIB_VSERVER=/usr/lib/util-vserver<br />
exec $USR_LIB_VSERVER/vsysvwrapper cups $*<br />
</pre> <br />
Do not forget to give a password to the root user, if you want to ba able to manage your printers from the web interface (http://yourcupsvserver:631)!<br />
<pre> <br />
# passwd root<br />
...<br />
</pre> <br />
If you use Mandriva 10.1 (And maybe some other distros), you&#8217;ll need to add the printers drivers for Cups, and reload it:<br />
<pre> <br />
# urpmi --root /vservers/yourcupsvserver/ cups-drivers<br />
# /etc/init.d/cups reload<br />
</pre> <br />
&#8230;It added 67 Mb of packages for me. <br />
<br />
Then use ''/etc/init.d/v_cups (re)start'' to launch Cups on the host server. <br />
You will now be able to make Cupsd start in the vserver , but more tweaking on the ACLs may be necessary to avoid authentification problems...<br />
<br />
=== Bind9 on Debian GNU/Linux Woody (3.0), Sarge (3.1), Etch (4.0) ===<br />
named provided by the bind9 binary packages fails to start because it is compiled with CAPs option. <br />
<br />
The debian way is to build** your own package without CAPs:<br />
<pre><br />
su -<br />
cd /usr/src<br />
apt-get build-dep bind9<br />
apt-get source bind9<br />
cd bind9-x.x.x<br />
vi debian/rules<br />
</pre> <br />
Insert the following line after "./configure --prefix=/usr \":<br />
<pre><br />
--disable-linux-caps \ <br />
</pre> <br />
On a NPTL-enabled system you alse have to replace <br />
<pre> <br />
--enable-threads \<br />
</pre> <br />
with<br />
<pre> <br />
--disable-threads \<br />
</pre> <br />
or bind might refuse to run with an other user than root. <br />
<br />
Save the file and go ahead with compiling/installing: <br />
<pre> <br />
dpkg-buildpackage<br />
dpkg -i ../bind9-x.x.x.deb<br />
echo "bind9 hold" | dpkg --set-selections<br />
</pre> <br />
The last line is to set the package "on hold", so it is not touched by the update process. you have to take care of security holes by yourself now! <br />
<br />
The Xs in "bind9-x.x.x" denote the version number of bind9. Alternatively you can allow the CAP_SYS_RESOURCE for that V-Server. The best way would be to fix bind, which is somehow broken when it comes to capabilities. Daniel Hokka Zakrisson repaired it. His patch is to be found here:<br />
<br />
[bind-9.3.2-caps-when-available.patch] ''need patch url please''<br />
<br />
So, if you recompile, it would be the cleanest way to apply that patch. Thanks Daniel! It would be also nice, if someone submits that patch to the bind people or maybe to your distribution's package maintainers in the first step.<br />
<br />
Get my [http://linux-vserver.derjohn.de/bind9-packages/bind9-capacheck_9.3.2-2_i386.deb vserver-guest-ready Debian bind9 package] for Debian Sid guests. Feedback welcome: aj@net-lab.net<br />
<br />
''Problems getting this to work in an x86_64 vserver. Any hints? From what I can tell from stracing, turning off threads doesn't fix everything related to it. It also caused a juicy Ksymoops.''<br />
<br />
=== Zimbra Mail ===<br />
Zimbra is many applications (including Postfix and MySQL? and OpenLDAP? and more) which try to take over the interfaces, and depend a lot on binding from 127.0.0.1 - it is not hard to change, but there is a couple of tricks - it is documented here - http://wiki.zimbra.com/index.php?title=Install_VServer<br />
<br />
=== xine ===<br />
won't start with no error message.<br />
<br />
"xine --verbose" shows this.<br />
<pre> <br />
ERROR: Could not determine network interfaces, you must use a interfaces config line<br />
</pre> <br />
This happens if you have the xineplug_inp_smb.so plugin. Delete it and everything is fine.<br />
<br />
=== 127.0.0.1 issues ===<br />
I had problems with an application that wanted me to access it on 127.0.0.1 and AS 127.0.0.1 to be able to do its configuration. A simple tweak solved the problem. I renamed the default interface directory "0" in /etc/vservers/server/interfaces to "1" and created interface 0 as :<br />
<pre> <br />
dev lo <br />
ip 127.0.0.1 <br />
mask 255.0.0.0 <br />
name lo <br />
</pre> <br />
now interface "1" is the default created interface by the vserver build script with a local adress like 192.168.1.2 and interface "0" is the loopback. I can now telnet on 127.0.0.1 and it sees that im connecting to 127.0.0.1 from 127.0.0.1<br />
<br />
Compiling nagios-1.4 within a vserver requires this, otherwise it hangs during the configure with "checking for ICMP ping syntax..."<br />
<br />
=== Hula-project ===<br />
Does not want to start. TODO: add more information.<br />
<br />
=== Postfix ===<br />
<br />
==== Postfix 2.1.5 (Debian Sarge) ====<br />
On a vserver with two interfaces (lo and eth0), and a postfix 2.1.5 listening on lo, postfix can't send emails : "Invalid argument"... Setting smtp_bind_address (http://www.postfix.org/postconf.5.html#smtp_bind_address) to the external address solves the issue. <br />
<br />
==== Postfix Policy Daemon ====<br />
Running a Debian 3.1 Sarge with Backports I have several issues with the postfix-policyd because it wants to set the rlimits.<br />
<br />
Log returns: <br />
<pre> <br />
cannot set rlimit: Operation not permitted<br />
</pre> <br />
Strace tells us:<br />
<pre> <br />
setrlimit(RLIMIT_NOFILE, {rlim_cur=4097, rlim_max=4097}) = -1 EPERM (Operation not permitted)<br />
</pre> <br />
Output on the Host<br />
<pre> <br />
# ulimit -Ha<br />
...<br />
-n: file descriptors 1024<br />
...<br />
</pre><br />
Thats too little...<br />
<br />
Solution:<br />
<br />
The App has again a build in need to use CAP_SYS_RESOURCE (which is bad (tm)) so in the guest do:<br />
<pre><br />
# ulimit -HS -n 8192<br />
# ulimit -Ha<br />
.. shows us now the correct 8192 instead of 1024.<br />
<br />
# vserver $yourVserverName restart<br />
# vserver $yourVserverName enter<br />
<br />
$yourVserverName # ulimit -Ha<br />
...<br />
-n: file descriptors 8192<br />
...<br />
</pre><br />
Everything should be fine now !</div>80.160.159.106http://linux-vserver.org/Installation_on_GentooInstallation on Gentoo2007-01-02T13:03:33Z<p>80.160.159.106: missing \</p>
<hr />
<div>== Host configuration ==<br />
<br />
=== Install a Linux-VServer kernel ===<br />
<br />
Installing a prepatched kernel is as easy as:<br />
<br />
<pre><br />
# emerge vserver-sources<br />
</pre><br />
<br />
However, the main portage tree only contains stable kernels (at the time of writing this is 2.0.x). If you want to install 2.1.1 or above, please take a look at the [http://overlays.gentoo.org/proj/vps/ Gentoo VPS Project Overlay] and [http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds Howto install 3rd party ebuilds].<br />
<br />
After the vserver-sources are installed it's time to configure them using make menuconfig. Below is a common configuration for 2.1.1 and above. If you are using 2.0.x some configuration options may not be present.<br />
<br />
<pre><br />
# cd /usr/src/linux-<KERNELVERSION>-vserver-<VSERVERVERSION><br />
# make menuconfig<br />
<br />
Linux VServer ---><br />
[ ] Enable Legacy Kernel API<br />
[ ] Enable Legacy Networking Kernel API<br />
[ ] Remap Source IP Address<br />
[*] Enable COW Immutable Link Breaking<br />
[*] Enable Virtualized Guest Time<br />
[*] Enable Proc Security<br />
[*] Enable Hard CPU Limits<br />
[*] Avoid idle CPUs by skipping Time<br />
[*] Limit the IDLE task<br />
Persistent Inode Tagging (UID24/GID24) ---><br />
[ ] Tag NFSD User Auth and Files<br />
[ ] Enable Inode Tag Propagation<br />
[*] Honor Privacy Aspects of Guests<br />
[ ] VServer Debugging Code<br />
</pre><br />
<br />
'''Note''': If you are using reiserfs as filesystem on the partition where guest images are stored, you will need to enable extended attributes for reiserfs in your kernel config and additionally add the attrs option in /etc/fstab.<br />
<br />
<pre><br />
File systems ---><br />
<*> Reiserfs support<br />
[*] ReiserFS extended attributes<br />
</pre><br />
<br />
<pre><br />
/dev/hdb1 /vservers reiserfs noatime,attrs 0 0<br />
</pre><br />
<br />
After you've built and installed the kernel, update your boot loader and finally reboot to see if the kernel boots correctly.<br />
<br />
<pre><br />
(Building the kernel)<br />
# make<br />
(Installing)<br />
# make modules_install<br />
# cp arch/<arch>/boot/bzImage /boot/kernel-<KERNELVERSION>-vserver-<VSERVERVERSION><br />
(Edit bootloader config file as required and)<br />
# reboot<br />
</pre><br />
<br />
=== Setup host environment ===<br />
<br />
To maintain your virtual servers you need the util-vserver package which contains all necessary programs and many useful features.<br />
<br />
<pre><br />
# emerge util-vserver<br />
</pre><br />
<br />
You have to run the vprocunhide command after every reboot in order to setup /proc permissions correctly for vserver use. An init script has been installed by util-vserver. To use it you should add it to a runlevel: <br />
<br />
<pre><br />
# rc-update add vservers default<br />
# /etc/init.d/vservers start<br />
</pre><br />
<br />
The vshelper script is used to restart virtual servers correctly. You have to tell the kernel where the vshelper script is located: <br />
<br />
<pre><br />
# echo 'kernel.vshelper = /usr/lib/util-vserver/vshelper' >> /etc/sysctl.conf<br />
# sysctl -p<br />
</pre><br />
<br />
== Guest configuration ==<br />
<br />
You have to download a vserver prepared stage3 from one of the [http://www.gentoo.org/main/en/mirrors.xml Gentoo mirrors]. Those stages are located under the experimental/<arch>/vserver/ directory. Since a stage3 contains a complete root filesystem you can use the template build method of util-vserver. However, this method is only available since util-vserver-0.30.211, so make sure you have the right version installed.<br />
<br />
You have to choose a context ID for your vserver (dynamic context IDs are discouraged) as well as the necessary network device information (In this example eth0 is configured with 192.168.1.253/24 and the context ID is equivalent to the last two parts of the virtual servers IP).<br />
<br />
<pre><br />
# vserver myguest build \<br />
--context 1253 \<br />
--hostname myguest \<br />
--interface eth0:192.168.1.253/24 \<br />
--initstyle plain \<br />
-m template \<br />
-t /path/to/stage3-<arch>-<version>.tar.bz2 \<br />
-d gentoo<br />
</pre><br />
<br />
You should be able to start and enter the vserver by using the commands below. If you miss commands like mount or dmesg you should emerge util-linux inside your virtual server as the vserver profile doesn't ship this package by default.<br />
<br />
<pre><br />
# vserver myguest start<br />
# vserver-stat<br />
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME<br />
0 90 1.4G 153.4K 14m00s11 6m45s17 2h59m59 root server<br />
1253 2 3M 286 0m00s45 0m00s42 0m02s91 myguest<br />
# vserver myguest enter<br />
# ps ax<br />
PID TTY STAT TIME COMMAND<br />
1 ? S 0:00 init [3]<br />
22887 ? Ss 0:00 /usr/sbin/syslog-ng<br />
20496 pts/0 S 0:00 /bin/bash -login<br />
20508 pts/0 R+ 0:00 ps ax<br />
# logout<br />
</pre><br />
<br />
== Maintenance made easy ==<br />
<br />
=== Start guests on boot ===<br />
<br />
You can start certain guests during boot. Each guest can be assigned a MARK. Now everything you have to do is configure these MARKs in the guests configuration and tell the init script to run all MARKed guests.<br />
<br />
<pre><br />
(Do this for every guest you want to start)<br />
# mkdir -p /etc/vservers/myguest/apps/init<br />
# echo "default" > /etc/vservers/myguest/apps/init/mark<br />
</pre><br />
<br />
'''Note''': Since all guests marked with "default" are started by default, nothing more has to be done. If you have different marks you should also update /etc/conf.d/vservers.<br />
<br />
=== Keep portage in sync ===<br />
<br />
The script vesync will help you to keep the metadata cache and overlays in sync. vemerge is a simple wrapper for emerge in guests.<br />
<br />
<pre><br />
(Sync metadata for 'myguest')<br />
# vesync myguest<br />
(Sync metadata for all guests)<br />
# vesync -a<br />
(Sync metadata for all guests except 'myguest')<br />
# vesync -a -e myguest<br />
(Sync 'myoverlay' for all guests)<br />
# vesync -a \<br />
--overlay /usr/local/overlays/myoverlay \<br />
--overlay-host rsync://rsync.myhost.com/myoverlay \<br />
--overlay-only<br />
(emerge app-editors/vim in 'myguest')<br />
# vemerge myguest app-editors/vim -va<br />
</pre><br />
<br />
=== Update guests ===<br />
<br />
Gentoo guests can share packages to save compilation time. In order to use shared packages, you have to create a central directory for packages on the host. We will use /var/cache/vpackages on the host and mount it to /usr/portage/packages in every guest.<br />
<br />
<pre><br />
# mkdir -p /var/cache/vpackages<br />
# $EDITOR /etc/vservers/myguest/fstab<br />
(Add this line at the end)<br />
/var/cache/vpackages /usr/portage/packages none bind,rw 0 0<br />
</pre><br />
<br />
Now you can use vupdateworld to update every guest. The command is equivalent to something like emerge --deep --update --newuse world depending on command line options.<br />
<br />
<pre><br />
(Pretend update for 'myguest')<br />
# vupdateworld -p myguest<br />
(Update 'myguest' using binary packages)<br />
# vupdateworld -k myguest<br />
(Update all guests using binary packages)<br />
# vupdateworld -ka<br />
</pre><br />
<br />
'''Note''': In order to get binary packages you can either use PORTAGE_BINHOST (see man make.conf) or set FEATURES="buildpkg" in one or more guests.<br />
<br />
After a successful update you can easily update all configuration files with vdispatch-conf. It is a simple wrapper for dispatch-conf and behaves exactly the same.<br />
<br />
<pre><br />
(Update configuration files for 'myguest')<br />
# vdispatch-conf myguest<br />
(Update configuration files for all guests)<br />
# vdispatch-conf -a<br />
</pre><br />
<br />
== External Resources ==<br />
<br />
Please take a look at the [http://www.gentoo.org/proj/en/vps/vserver-howto.xml Gentoo Linux-VServer Howto] for more information. In general we try to keep the wiki in sync, nevertheless it might help :)</div>80.160.159.106