About this list Date view Thread view Subject view Author view Attachment view

From: Bjoern Steinbrink (bjoern.steinbrink_at_isp4p.net)
Date: Tue 03 Feb 2004 - 01:04:54 GMT


On Tue, 2004-02-03 at 01:58, Tor Rune Skoglund wrote:
> > > I noticed that when starting a command like this in the root server:
> > >
> > > chcontext --ctx 110 mysql -u username -p -h myhost
> > >
> > > The IP address is not changed. Access to the mysql database is not
> >
> > To change the IP you must run chbind ;)
> Errr...? If you run a command in an already running vserver, should that
> command run in the environment of that vserver, which also includes
> that context's IP?

If I got it right, the context and ip binding is process bound. What the
vserver script does is to setup an initial process bound to a specific
context and ip adress(es) that then fires up the vserver, as the childs
inherit the context/ip bindings you get everything inside the vserver
bound to that context/ip.

Just calling chcontext will bind the new process to the context
specified, but not to an ip address, as the ip bindings do not belong to
a context but only to processes. (Actually, if the calling process is
bound to an ip address the new process will also be bound to that

If you had a running vserver in context 123 with ips and, you could start a process xyz in that context that is only
bound to ip but not by issuing

chcontext --ctx 123 chbind --ip xyz

from within the root server. By issuing

chcontext --ctx 123 chbind --ip xyz

you can even start a process inside context 123 that is bound to although from within the 'vserver' you do not have access to
this ip adress.

What I'm basically trying to say is: context != vserver ;)

Bjoern Steinbrink

Vserver mailing list

About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Tue 03 Feb 2004 - 01:06:13 GMT by hypermail 2.1.3