From: Jacques Gelinas (jack_at_solucorp.qc.ca)
Date: Thu 08 Aug 2002 - 21:43:42 BST
On Tue, 6 Aug 2002 17:27:50 -0500, Ian Douglas wrote
> > so short answer to your question:
> > - call v_xxx in your main server to limit
> > the services to the given ip(s)
> > - call xxx in your virtual servers because
> > the chbind is already in effect
>
> Thanks, that's what I was looking for.
There should not be any v_xxx script in a vserver anyway. They get there because
people most of the time create a vserver by cloning the root server, so they got copied
there. The v_xxxx script have no purpose at all on a vserver. A vserver is tied
to one or more IP and has to use only those. A root server has access to all, so the
v_xxx script were created to limit the scope of a given service easily. See below
> > if [ -f /etc/vservices/sshd.conf ] ; then
> > . /etc/vservices/sshd.conf
> > fi
>
> Why would this come into play though? Extra configuration of some kind? Is
> it the same as the .conf files otherwise found in just /etc/ ?
The /etc/vservers/*.conf are used only for the root server. Normally, for new
projects, the root server does not run any service, or at most sshd. As such
it does not conflict with any vservers. But most people start from a live server
already having some service and then add few vservers. So they have to
limit the scope of the services in the root server. By default, the v_xxx script
limit to one IP: the main IP of the eth0 device. This may be a problem for
some server. Maybe you want eth1 or more than on IP. So you can create
a file /etc/vservices/xxx.conf and enter
IP=whatever_IP
Note that version 0.18 do not support multiple IP there. I just fixed it. While doing
so I reworked all the v_xxx scripts to use a common helper script, so they are
less redundant.
---------------------------------------------------------
Jacques Gelinas <jack_at_solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!
http://www.solucorp.qc.ca/miscprj/s_context.hc