On Sun, Apr 23, 2006 at 02:23:47PM +0200, Kurt Roeckx wrote:
> I can atleast explain 1 problem:
> > test test_socket failed -- Traceback (most recent call last):
> > File "/build/buildd/python2.4-2.4.3/Lib/test/test_socket.py", line 449,
> > in testSockName
> > self.assertEqual(name, ("0.0.0.0", PORT+1))
> > AssertionError: ('83.143.242.5', 50008) != ('0.0.0.0', 50008)> It's running in a vserver, and 83.143.242.5 is the address > of the vserver. You won't be able to bind to 0.0.0.0. Erm. That sounds like a buggy vserver implementation to me; binding to 0.0.0.0 is a normal Unix practice, and while I understand that a vserver process shouldn't necessarily be allowed to bind to all interfaces on the machine, it seems to me that this ought to be done via a transparent mapping in the kernel instead... -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
