W dniu 22.09.2010 16:36, Doug Coleman pisze:
Hi,
I recently made it a requirement that a server either start on all the ports
specified or none of them. The server code attempts to bind to and
immediately close an ipv6 port, and if it's successful, a server will also
bind ipv6. Binding
(...) listening on ip6 port. So, there's an issue with concurrent threads.
listening on separate address spaces.
D.
... on the same port (I mean as numeric value). Experimentally, I've
changed set-servers to mutate ip6 address port (+1) and threads had no
problems with start. Up and
W dniu 22.09.2010 12:59, Damian Dobroczyński pisze:
Hi list!
I tried to run counter web application example and whatever port I tried
to run it on I got Address already in use (98). Then I tried to run an
empty (without main-responder set) httpd server using httpd
and such but it
W dniu 22.09.2010 15:54, Damian Dobroczyński pisze:
W dniu 22.09.2010 12:59, Damian Dobroczyński pisze:
Hi list!
I tried to run counter web application example and whatever port I tried
to run it on I got Address already in use (98). Then I tried to run an
empty (without main-responder set)
Hi,
I recently made it a requirement that a server either start on all the ports
specified or none of them. The server code attempts to bind to and immediately
close an ipv6 port, and if it's successful, a server will also bind ipv6.
Binding the same port on ipv4 and ipv6 shouldn't be a
2010/9/22 Damian Dobroczyński qoo...@gmail.com:
My system is
Ubuntu 10.04 and is sane. Did you have similar issues before? Please, help.
I get this same issue on Ubuntu 10.04. Can you share the workaround
you did to stop the ipv6 binding?
Chris.
--
http://www.bluishcoder.co.nz
