Too long on a BSD box SO_REUSEPORT is specific to it :)
If SO_REUSEADDR there should be no reason the restarting process cant bind to the address. Someone suffering from this problem should check the state of the port using OS utils netstat / sockstat / lsof to see what's holding the port and what state it is in.
The rules state that if SO_REUSEPORT is set then only if the port is in the LISTEN state should binding be refused if the OS thinks it is in LISTEN but to a dead process then there is something wrong on the OS side which would be odd but not impossible.
If anyone has a server in this situation and needs help looking at it give me a shout on IRC #mpukhosting on QuakeNet.
If we can give Alfred / the guys at valve a reproducible / solution to this I'm sure they would be more than happy to fix it :)
Steve / K ----- Original Message ----- From: "Alfred Reynolds" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, December 16, 2004 6:47 PM Subject: RE: [hlds_linux] RCON Problems with CS:S
SO_REUSEPORT isn't a valid sockopt and SO_REUSEADDR is already used.
- Alfred
----Original Message---- From: [EMAIL PROTECTED]
If I hear u correct that will be just someone not specifying: SO_REUSEADDR|SO_REUSEPORT when the port is created. and hence would be a 30second fix.
================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED]
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
