hmmm... just for fun yesterday we tested squid (from debian sarge) in a vserver - squid was running "out-of-the-box", even with squidguard there was no problem. we are using kernel 2.6.7 with vs1.9.2-rc10 and we didn't grant any extra privilege to this vserver.
inside a vserver you can bind to 0.0.0.0 without any problem, you should only care about ip addresses at the host side. if your vserver is configured right and already running other (working) services and your host doesn't use ports needed by squid in your vserver your problem is probably squid-related - no error in the logs? cheers thomas Am Mi, den 18.08.2004 schrieb jfl um 2:53: > Hello again, > > Thanks to Christian Mayrhuber I am running bind in a vserver... but now > I am having trouble with squid. > > Squid runs, but does not accept connections. > > I thought that I had read that vservers strove with their hosts if > configured to list at IP address 0.0.0.0, so I changed what seemed to be > the relevant 0.0.0.0 addresses in squid.conf to the squid's vserver IP > address, but I still cannot connect to the squid using either a > requesting browser or via telnet. > > I haven't found any reference to squid in the FAQs or in the last year's > archives. > > Any help would be appreciated. > > Thanks. > > _______________________________________________ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver -- Thomas Gelf <[EMAIL PROTECTED]> _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
