Egbert Eich wrote:
When creating an IPv6 socket on Linux an IPv4 socket seems to be
created also.
The current CVS code produces the error:
_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
bind() returns an EADDRINUSE error when binding to the second IP
protocol (in CVS it is IPv6).
When I switch the order of initialization around and skip the IPv4
protocol if IPv6 initialization was successful, everything works:
I can connect thru IPv6 and IPv4.
This was one of the patches suggested to the X.org IPv6 review which
we declined to include in our patch set, but which got checked into
the XFree86 CVS anyway. We were told that separately binding to both is
the usual habit on OpenBSD, while simply binding to IPv6 and letting it
handle both was the way we coded it to work, and had it working on both
Solaris and Linux.
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - Sun Software Group
Quality / User Experience (QUE) - Globalization
Platform Globalization Engineering: X11 Development
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
