From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Tue 05 Nov 2002 - 01:27:03 GMT
if newvserver is used to clone a server from the
root (physical) installation, the script fails
with the following message ...
--------- SNIP ---------
Server TEST was installed in /vservers/TEST
The configuration file /etc/vservers/TEST.conf was created
The script /etc/vservers/TEST.sh was created
Vserver TEST was created in 2 seconds
Virtual server /vservers/TEST already exist
---------
this is caused by creating the server configuration
and script files in /etc/vservers first, and then
calling the <vserver> utility with the build option
(which refuses to create the server it believes
already existing ...)
--------- SNIP ---------
echo "esac" >>$SCRIPT
chmod +x $SCRIPT
LOG=/var/run/newvserver.log.$$
if [ "$clone" = "/" ] ; then
# Unification does not work on / yet
$VSERVER_CMD $name build >$LOG
elif [ "$clone" = "#rh7.2" ] ; then
check_cd "first RedHat 7.2 CD"
set_fstab $VROOT
installpkgs $LOG $USR_LIB_VSERVER/install-rh7.2 $name
...
--------
workaround: use "vserver <name> build" instead of
the newvserver tool ...
best,
Herbert
PS: if this issues is already known, please ignore
this posting, but I could not find any evidence in
my archives of the vserver mailing list ...