Subject: Re: [vserver] localhost - The Cliff Notes version?
From: "Vince M. Clark" <vclark@globalera.com>
Date: Tue, 12 Feb 2008 07:03:50 -0700 (MST)
Tue, 12 Feb 2008 07:03:50 -0700 (MST)
I always point it to 127.0.0.1 regardless of how many guests I have on the host. Not
sure if this is good or bad practice. 

----- Original Message ----- 
From: "Roderick A. Anderson" <raanders@acm.org> 
To: vserver@list.linux-vserver.org 
Sent: Monday, February 11, 2008 9:22:44 PM (GMT-0700) America/Denver 
Subject: Re: [vserver] localhost - The Cliff Notes version? 

Vince M. Clark wrote: 
> I'm a jack of all trades, master of none so my depth of knowledge with 
> vserver is limited. But I do use it on a Debian host, and every time I 
> create a vserver I always add localhost to /etc/hosts. I've never 
> understood the underlying reasons for why I must do this, I just know 
> that it usually solves my problem with most apps. The only exception is 
> Zimbra. I beat my head against the wall for days trying to get Zimbra to 
> install on a vserver and finally gave up and allocated dedicated hardware. 
> 
> I guess my point is that I haven't run into an application yet that has 
> a localhost problem except Zimbra. Is there a deeper localhost problem 
> than simply adding it to /etc/hosts? 

Do you add it as 127.0.0.1 or 127.0.0.x where x is different for each guest? 

I have also just added it and seen no problems that I can identify. 

Plus I've made localhost point to the guest's real IP for some 
applications and made sure, for others, there were no references to 
localhost in the application's conf file(s). 

I didn't want to cause a ruckus but was concerned that I still don't 
really understand why the lo interface is so special. Therefore the 
request for a user-dummy insight. Of course I am a Linux-Vserver user 
(not a fifth degree network-guru) so that is probably why I don't get it. 

It has become more of an issue for me as I've been creating 2-3 guests a 
week for the last month or so and therefore seeing the odd messages more 
often. 


Rod 
-- 
> 
> Vince Clark 
> Global Era 
> The Freedom of Open Source 
> vclark@globalera.com 
> (303) 493-6723 
> 
> ----- Original Message ----- 
> From: "Jason Drage" <jasond@ibsglobalweb.com> 
> To: vserver@list.linux-vserver.org 
> Sent: Monday, February 11, 2008 5:59:02 PM (GMT-0700) America/Denver 
> Subject: Re: [vserver] localhost - The Cliff Notes version? 
> 
> 
> > I've hacked my way through this but I think from watching this list 
> > there must be an easier way to get around the messages/errors. 
> This is exactly the issue I have with vserver localhost - we shouldn't 
> have to hack applications or installers. 
> Far better to fix this in one place - the vserver code - rather that 
> have every admin have to hack every application that assumes localhost 
> will function like it always has. 
> 
> -- Jason 



I always point it to 127.0.0.1 regardless of how many guests I have on the host. Not sure if this is good or bad practice.

----- Original Message -----
From: "Roderick A. Anderson" <raanders@acm.org>
To: vserver@list.linux-vserver.org
Sent: Monday, February 11, 2008 9:22:44 PM (GMT-0700) America/Denver
Subject: Re: [vserver] localhost - The Cliff Notes version?

Vince M. Clark wrote:
> I'm a jack of all trades, master of none so my depth of knowledge with
> vserver is limited. But I do use it on a Debian host, and every time I
> create a vserver I always add localhost to /etc/hosts. I've never
> understood the underlying reasons for why I must do this, I just know
> that it usually solves my problem with most apps. The only exception is
> Zimbra. I beat my head against the wall for days trying to get Zimbra to
> install on a vserver and finally gave up and allocated dedicated hardware.
>
> I guess my point is that I haven't run into an application yet that has
> a localhost problem except Zimbra. Is there a deeper localhost problem
> than simply adding it to /etc/hosts?

Do you add it as 127.0.0.1 or 127.0.0.x where x is different for each guest?

I have also just added it and seen no problems that I can identify.

Plus I've made localhost point to the guest's real IP for some
applications and made sure, for others, there were no references to
localhost in the application's conf file(s).

I didn't want to cause a ruckus but was concerned that I still don't
really understand why the lo interface is so special.  Therefore the
request for a user-dummy insight.  Of course I am a Linux-Vserver user
(not a fifth degree network-guru) so that is probably why I don't get it.

It has become more of an issue for me as I've been creating 2-3 guests a
week for the last month or so and therefore seeing the odd messages more
often.


Rod
--
>
> Vince Clark
> Global Era
> The Freedom of Open Source
> vclark@globalera.com
> (303) 493-6723
>
> ----- Original Message -----
> From: "Jason Drage" <jasond@ibsglobalweb.com>
> To: vserver@list.linux-vserver.org
> Sent: Monday, February 11, 2008 5:59:02 PM (GMT-0700) America/Denver
> Subject: Re: [vserver] localhost - The Cliff Notes version?
>
>
>  > I've hacked my way through this but I think from watching this list
>  > there must be an easier way to get around the messages/errors.
> This is exactly the issue I have with vserver localhost - we shouldn't
> have to hack applications or installers.
> Far better to fix this in one place - the vserver code - rather that
> have every admin have to hack every application that assumes localhost
> will function like it always has.
>
> -- Jason