From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Fri 03 Sep 2004 - 15:27:46 BST
On Fri, Sep 03, 2004 at 12:15:08PM +0200, Arne Blankerts wrote:
> On Fri, 2004-09-03 at 00:55, Roderick A. Anderson wrote:
> > > b) when the last process in a context dies, the context
> > > is automatically removed and with it the 'notion' of
> > > a virtual server
> As you quote my fc1-howto, you might reread the section about the
> services one wants to start: A (v)Server whithout at least syslog
> running is not a complete unix environment. So at least syslog should
> be set to active in ntsysv (or via chkconfig manually). Having a syslog
> in each vserver keeps the context 'active' and thus visible in
> > > so what happens here is not that the vserver is 'idle'
> > > because there is no service running inside, it actually
> > > does only exist for a few seconds, and vanishes then ...
> > >
> > > now the expected question, why does it respond to ping
> > > then? it doesn't and probably vservers will never respond
> > > to pings, but the interface address/alias is configured
> > > and as usual the host will answer a ping ...
> > I know that!!! I was thinking that if 'vserver xxx start' failed the
> > ifconfig would not work so there would be no interface to ping against.
> Erm.. who said it failed? The vserver startup works just fine, but since
> no processes are running within the context, you can't see anything.
> That has NO effect whatsoever on the ip binding.
hmm, guess this is a philosophical question:
does an ip binding still exist, even when the vserver
context is gone for a while and there is no process
'bound' with that binding?
I'd tend to say it doesn't exist anymore, but YMMV ;)
> Mit freundlichen Grüßen/Regards,
> Arne Blankerts
> SalesEmotion GmbH
> Arne Blankerts
> Head of Development
> Afrikahaus :: Große Reichenstraße 27 :: 20457 Hamburg
> Tel. +49 40 20 000 2-0 :: Fax +49 40 20 000 2-22
> blankerts_at_salesemotion.de :: www.salesemotion.de
> Vserver mailing list
Vserver mailing list