Hello

On Tue, Apr 19, 2005 at 10:24:55AM +0200, Daniel Hermann wrote:
> Hi,
> 
> On Mon, Apr 18, 2005 at 11:25:25PM +0200, Ola Lundqvist wrote:
> > 
> > ...
> > 
> > Ok. The problem is that vserver ... build do more restrictive checks:
> > zircone:/etc/vservers# newvserver --hostname test --domain 
> > intranet.opal.dhs.org --ip 192.168.254.200
> > s_context: 0
> > vserver-topdirectory '/srv/vservers/test' and/or configuration at 
> > '/etc/vservers/test'
> > exist already; please try to use '--force', or remove them manually
> > newvserver: error: vserver-build failure. Cannot continue.
> > 
> > I use LVM to create install partitions. I have to fix that.
> > 
> 
> Yes, it refuses to build the new vserver if it finds a directory of
> the same name, even if this is empty.

I noticed that. I have to fix util-vserver then... :)

> > > -# This is used to keep a cache of the downloaded .deb packges for next 
> > > install
> > > -if [ -d "$VROOTDIR/ARCHIVES/$DIST" ]; then
> > > -    mkdir -p "$VROOTDIR/$VHOST/var/cache/apt/archives"
> > > -    cp -a "$VROOTDIR/ARCHIVES/$DIST/"*.deb 
> > > "$VROOTDIR/$VHOST/var/cache/apt/archives" > /dev/null 2>&1
> > > -fi
> > 
> > Why did you remove this?
> > 
> 
> It didn't work any more, for the same reason as above I guess. The
> directory for the vserver is created before "vserver ... build" is
> called, so it refuses to run.

I thought that may be the problem. I just wanted to check if there were
any other reason for this. I'll put it back and fix util-vserver then.

> > 
> > ...
> > 
> > > -S_CAPS="CAP_NET_RAW"
> > 
> > Do you know if this is still the default? I need to know if I should close
> > yet one more bug with this upload. :)
> > 
> 
> I don't know. I think we should translate the code where
> vserver-name.conf is created into the new configuration scheme, then
> we are on the safe side.

Ahh that is not handled by vserver ... build?

> > ...
> > >  
> > >  EOF
> > >  
> > > +## start vserver before we can exec anything inside it
> > > +vserver $VHOST start
> > 
> > Do we need to start it? Is this something new?
> > 
> 
> Yes. It's not possible any more to enter the vserver or exec anything
> without starting the vserver.

Ok.

> > ...
> > > -# Populate the archive for future virtual servers
> > > -if [ ! -d $VROOTDIR/ARCHIVES/$DIST ]; then
> > > -    mkdir -p $VROOTDIR/ARCHIVES/$DIST
> > > -fi
> > > -cp $VROOTDIR/$VHOST/var/cache/apt/archives/*.deb $VROOTDIR/ARCHIVES/$DIST
> > 
> > This is removed because you remove the above...
> > 
> 
> Right.

Regards,

// Ola

> regards
> 
>       Daniel
> 
> -- 
> -----------------------------------------------------------------
> Daniel Hermann,   Institut fuer Theorie der Kondensierten Materie
> Universitaet Karlsruhe                  Tel: ++49 (0)721 608-3588
> Postfach 6980                           Fax: ++49 (0)721 608-7779
> 76128 Karlsruhe, Germany      email: [EMAIL PROTECTED]
> -----------------------------------------------------------------
> 
> 

-- 
 --------------------- Ola Lundqvist ---------------------------
/  [EMAIL PROTECTED]                     Annebergsslingan 37      \
|  [EMAIL PROTECTED]                 654 65 KARLSTAD          |
|  +46 (0)54-10 14 30                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to