Just Nalin/Joey/Cadavre as far as I know 
There are more people who possess both the skill and the know-how, like 39ster, who started the whole GR server base. Just of all the people who know what they are doing, only a few are active most of the time and even they have lives aside from Reborn.
uh, anyone can host a list server. its just a matter of all of us agreeing to use just 1, which happens to not work. haha
Yeah hosting it is the easy part. Developing it to work with the newer clients and features is not.
Merged doublepost_______________
Besides if more people hosted it it would only split the community and divide our player-count up even further as if that can be any lower. Probably centralization is our strongest asset at least for now.
It has been fixed. I’ll tell you what went wrong in a bit. I have to fix a computer.
Merged doublepost_______________
Okay. Cadavre had wanted me to add a new feature to the gserver and listserver that lets him use it on a multi-homed server (multiple NIC cards, ie, multiple IP addresses.) I added the feature to the gserver just fine, but when I looked at the listserver, I noticed that it was using a very old version of my CSocket class. I replaced the listserver’s version with my new one and implemented the feature.
Now, both the old CSocket and the new CSocket class had a bug in the getData() function involving non-blocking sockets. If you tried to getData() on a non-blocking socket that had no data, it would return an error code that basically said, “Hey, there is no data here!” The CSocket class would then disconnect the socket because of the error. This issue was masked because the old CSocket class had a broken non-blocking socket implementation! Since the sockets were being created as blocking sockets, it would never run into that error.
In the gserver, all the sockets are placed under a select() function. This blocks until a socket receives data. The listserver doesn’t do this. So, when I added the new CSocket class, it was trying to read data on a socket without data, then erroring and disconnecting it.
I fixed it by adding in support for the “Hey, there is no data here!” error code. It won’t disconnect the socket if it sees that error code. All is happy in Graal Reborn land now.
So nice !!! Thanks alot Nalin 
!!!
yay! the list-server is back. Thanks Nalin.
Wow what a tricky bastad of a bug. Nice work finding it!
does the client only accept ip addresses, or can it take domain names too? if it can do domain names then there can be redundant list servers just in case something like this happens again.
It can accept domain names, but it doesn’t check all IPs associated with that domain name.
Beholder and Downsider have done GServer stuff, too.
Does npcserver-v1 need CSocket fixed too?
Would that means that npc-server-v1
pcserver-v1\trunk
pcserver\src\CSocket.cpp would need to be fixed too?
fairly sure it uses a newer version of the class…
If the NPC-Server uses the CSocketManager class to manage its sockets, then it should be fine as it uses select() to wait for data to arrive on the socket instead of just polling it. But I should probably update it with the fix.
dude its sweet that you fixed it. i have only done a little client-server stuff in perl but not with different types of socket connections. thanks!