Editing
Linux-vserver administrators guide
(section)
From Linix VServer
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== C. Configuration host server == '''1. Configuring vserver''' After installing a customized kernel and the vserver or util-vserver tools, you can find the configuration options in the file: /etc/vservers.conf configuration options: <ul> <li>BACKGROUND= yes | no Start the vservers on tty9, in background so the rest of the boot process ends early.</li> <li>VSERVERS_ROOT= <path to vservers> (only in vserver package) This sets the location of the vservers. In case it's empty, the default value is /vservers. The util-vserver package doesn't use this option. Its location of the vservers is set during the installation of util-vserver.</li></ul> '''2. Daemons on the host server''' The daemons running on the host server will by default bind to all interfaces on the machine, including the alias interfaces used by the vservers. This will result in conflicts between the daemons running on the host system and the daemons running in the vservers. To solve this, we have to bind the daemons running on the host server to the IP-number of the host server. This can be done by using the wrapper scripts provided by the vserver tools or util-vserver packages. A alternative can be changing the configuration of the daemons. Some daemons (ssh, xinetd) have a configuration option to bind the on one interfaces. 2.1. Startup wrapper scripts On systems using system V startup scripts (like redhat), you can use wrapper scripts to bind the daemons to one interface. Replace inetd with xinetd. <ul> <li>v_gated.sysv</li> <li>v_httpd.sysv</li> <li>v_named.sysv</li> <li>v_portmap.sysv</li> <li>v_sendmail.sysv</li> <li>v_smb.sysv</li> <li>v_sshd.sysv It's a good idea to avoid the use of the v_sshd wrapper en use the configuration described in section 2.2.</li> <li>v_xinetd.sysv</li></ul> 2.2. Configuring daemons Use this option in case the startup wrapper scripts don't work on your distribution, or you don't want to change the startup scripts of your daemons. <ul> <li>SSH config file: sshd_config ListenAddress[[ListenAddress?action=edit|?]] 192.168.1.20</li> <li>inetd/xinetd You can't bind inetd to a interface, replace it with xinetd. config file: xinetd.conf defaults { bind = 192.168.1.20 }</li></ul> <span id="d.-virtual-hosts"></span>
Summary:
Please note that all contributions to Linix VServer may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Linix VServer:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Page actions
Page
Discussion
Read
Edit
History
Page actions
Page
Discussion
More
Tools
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
About
Overview
Paper
News
Developers
Donations
Search
Getting Started
Downloads
FAQs
Documentation
Support
Participate
How to participate
Report a Bug
Communicate
Teams/Projects
Hall of Fame
Resources
Archives
Recent Wiki Changes
Pastebin
Related Projects
VServer Hosting
Happy VServer Users
Tools
What links here
Related changes
Special pages
Page information