On Wed, Aug 20, 2003 at 02:30:29PM +0100, Sam Vilain wrote: > [incredibly important stuff left out] > > In a vserver context with IP restrictions (assuming Alex/Herbert > haven't changed this on me :)), when a process tries to bind to
huh? never ever touched the networking code ... hmm, maybe I should ... 8-) > 0.0.0.0, it is transparently altered to a bind to the primary address > of their vserver. This bind call fails, because another process > already has it open. > > There are three simple solutions; > > 1. run the daemon (postgres) with `chbind' to restrict it from > binding to anything other than the master server's IP address - > done by editing the /etc/init.d/* script. > > 2. configure the daemon to restrict it's binding to the master > server's IP address, see the manual. > > 3. turn off the daemon in the master server, perhaps it is not > needed > > (Paul - I couldn't see the answer to this common `bind failed' message > in the FAQ - perhaps it deserves an entry?) > -- > Sam Vilain, [EMAIL PROTECTED] > > I would have said yes to abortion if only it was right. I mean, yeah > it's right. Well no it's not right that's why I said no to it. > - George W. Bush, South Carolina, February 14, 2000 > >
