This is normal. Unless two vserver are sharing some IPs, they are allowed to do a bind(0.0.0.0) on the same port and it will show this way. So this is a little strange in the root server, but perfectly ok in the vserver.
This optimization may go away, maybe, when we will attack the per vserver private network loopback. Depending on the solution selected, the common case may become two IPs per vserver (the loopback and the main IP).
I have not done any benchmark with the new bind(any) stuff. It might be a little slower. Potentially not visible. Comments welcome.
There is a TAB in the form to enter up to 4 directories to exclude.
This avoids having all your vserver ending with the same sshd private keys...
where stuff in square bracket is optional.
Now even if you are not using fakeinit, /var/run/utmp is properly initialized with the proper runlevel (as found in /etc/inittab).
This problem was specific to /var/log (and everything under) as far as I can see, so this is hard-coded in the vrpm script.
There are two ways to select a profile:
Once you have started a vserver with a given profile, it is stored in the /var/run/vserver/XX.ctx file, so you can enter and stop the vserver using the active profile, even if you have changed the profile value in the configuration file.
The newvserver tool has been modified so you can immediately enter the second profile value. By default, one profile is called prod and the other is called backup.
vservers may be used as a fail-over strategy where whole servers may be switched on and off on the fly. Now one may use some synchronization tool (rsync ?) to make sure the backup is up to date. Sometime, it is not enough and you wish to maintain the backup in sync with the production vserver in real-time or almost. To perform that, you need to enable the backup server, but you can't do that unless you provide different network setting (avoid having two vserver running with the same IP). So the profile concept was introduced.
When starting a vserver using a given profile, the environment variable PROFILE is defined so you can perform various action such as exchanging key configuration file, starting services differently and so on.
Linuxconf users may want to enable the switchprofile pseudo service (available lately) to switch between different configuration file set.