[vserver] Understanding localhost

From: John A. Sullivan III <jsullivan_at_opensourcedevel.com>
Date: Fri 01 May 2009 - 09:48:12 BST
Message-Id: <1241167692.6353.10.camel@jaspav.missionsit.net.missionsit.net>

Hello, all. I'd like to confirm that I understand the way vserver 2.3
is handling localhost and the loopback address.

Am I correct to understand that, unlike earlier version, the default
kernel compilation makes it safe to use on a guest? That is,
each one is uniquely mapped and does not interfere with the host
listening in We can thus set our /etc/hosts files to use: localhost localhost.localdomain etc . . .?

However, is it also true that daemon bindings to localhost will still be
made to the address in /etc/vservers/<guest>/interfaces/0 and will not
include unless explicitly bound?

I ask because we were delighted to realize we could simplify our zimbra
installation by leaving /etc/hosts at for localhost. We then
started retrofitting our other servers to do the same. Some of our
servers communicate with sshd on We had changed the
configuration files to bind them to the non-loopback address, e.g., because of our old understanding of We also
changed sshd_config by removing the ListenAddress so that
it goes back to the default of binding to all interfaces.

This broke those applications. When we do a netstat -tln on the vserver
guests, it shows sshd listening only on (as an example) and
not That's fine and we can accommodate it by leaving our
settings as they were but I wanted to make sure I hadn't missed
something. Thanks - John

John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
Making Christianity intelligible to secular society
Received on Fri May 1 09:48:07 2009
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Fri 01 May 2009 - 09:48:08 BST by hypermail 2.1.8