From: Sam Stickland (sam_ml_at_spacething.org)
Date: Mon 24 Nov 2003 - 13:38:35 GMT
----- Original Message -----
From: "Bert De Vuyst" <bert.devuyst_at_intec.UGent.be>
Sent: Monday, November 24, 2003 1:34 PM
Subject: [Vserver] vrpm code questions
> After looking at the code of tool vrpm (part of vserver and util-vserver),
> have some questions.
> 1. The location of /vservers is hardcoded in this tool.
> I think it's at better idea use the option VSERVERS_ROOT=/vservers in this
> script and to use $VSERVERS_ROOT inside the script.
> In case of the vserver package by Jacques, the next lines
> if [ -f /etc/vservers.conf ] ; then
> source /etc/vservers.conf
> would be a usefull idea to set the $VSERVERS_ROOT.
> 2. In case the vserver is not running, the script starts a new security
> context. Correct me if I'm wrong, but I think it's not a good idea.
> Why? Some people have a backup of there vservers on a spare machine in
> there serverhardware fails. If they run vrpm on the spare machine, vrpm
> startup the vservers to update the packages. This can cause a problem as
> IP-address of the vserver is in use by the vserver running on the master
> server, and you end up running 2 vservers using the same IP-address.
> I think it would be beter to use chroot to run rpm in case the vserver is
I think that it's better that vrpm is ran in it's own security context,
rather than just a chroot jail. But a security context can be started
without starting the fakeinit can't it?
Vserver mailing list