From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Sun 23 Nov 2003 - 21:43:28 GMT
On Sun, Nov 23, 2003 at 10:04:08PM +0100, Dariush Pietrzak wrote:
> > so here is a nice log of a commBind?
> > which has troubles with what? version of vserver
> Here is a nice log squid
> having problem with binding to port 0 ( ie binding to any port )
> on specified IP.
> The problem is - vserver let's you bind only to 0.0.0.0:0,
> and not to given IP.
> > sorry, my magic glass ball is broken ...
> damn those developers, in the old days everyone used to have at least two
> spare, and now the only response seems to be "I'm not a clairvoyant".
what should I say, my spares where never replaced
by the budget cutting management ;)
> > please add some info ..
> And a simple program that triggers the problem?
> Well, it goes like this: you get the ctx17e patched kernel, install vserver
> debian package, create clean vserver instance containing squid cache.
hmm, well, maybe I should suggest to use _at least_
vs1.00 again ;) ... ctx17e was some kind of interrim
version, never intented as a production release ...
> The key seems to be that I bind the server to all IP ( i do not
> specify IPROOT because I need vserver bind to two IPs )
> (oh, btw, how about request for a feature - ability to specify more then
> one IP in iproot? I've got machine with a dozen ips, and would like to bind
> to only two of those).
okay, although no magic ball, my time machine is
still working, and so I managed to add this feature
to ctx-12 without anybody noticing ... enjoy!
> Ergh, I think I need to get some sleep and write everything again in a
> little bit more friendly and clear way ;) sorry.
no problem with that ...
> Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9
> Namagumi namagomi namagoroshi
> Vserver mailing list
Vserver mailing list