Xavier Cartron writes: > Here is the result in the log > > Ceci est le serveur pour Freeciv version 2.4.2 > Vous pouvez en apprendre davantage sur Freeciv sur http://www.freeciv.org/ > 3: in log_init() [log.c::231]: log started > 0: in server_open_socket() [sernet.c::1146]: bind failed: Adresse déjà > utilisée > 0: bind failed: Adresse déjà utilisée
An obvious difference between a standalone server and client-started one is that the former defaults to port 5556 and the latter to port 5557 or higher (in 2.4.2; history at <http://gna.org/patch/?4471>). So, what happens if you do "freeciv-server -p 5557"? This is weird in any case; the client is supposed to find a free port to start the server on, so this shouldn't be able to occur. > 'lsof -i -n -P' shows only this : 'netstat -a --ip' might be a better diagnostic, as it will show ports that are in TIME_WAIT state and the like. Does it matter what you've done previously? I'm wondering if TIME_WAIT might be causing trouble. Do you get this the very first time you launch the client after boot, or several minutes after you last quit any freeciv-related program? (We messed around with our socket binding upstream recently and we think we've exposed TIME_WAIT trouble, but that's in 2.5 and not 2.4 -- <http://gna.org/bugs/?21583> -- so can't possibly affect the Debian package, and in any case smells different.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org