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?
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
Received on Tue Feb 12 01:30:23 2008