I've been running the newer binary from Chris for the server for several hours now and haven't run into any major problems. Some stuff I mailed to Chris which I probably should have just put here in the first place:
>Some initial feedback: > >My 12 children started up and people immediately started joining. In >the parent console, I saw this a few times while the children were >still coming up: > >threadtools.cpp (417) : Assertion Failed: Thread synchronization >object is unuseable > >But after all the children had started, I didn't see it again. (I'm >running CentOS with 2.6.18.) > >The parent console seems to get a copy of every console message from >the children, which could be useful, but there's no way to tell which >child each line is from. So, it would be nice if each line started >with the child's ID. The parent netcon seems to get a selection of >each child's console messages, but I don't know which kinds of >messages and it also has no way to distinguish. > >For the parent's netcon, it would be nice if the status display would >say what each child's hostport (and maybe hostname) is, to make it >easier to figure out which child is which server. Maybe also add the >child's ID to the status display for each specific server (and maybe >show it in clients' status displays). In addition, the PID displayed >for each child matches the child ID (at least initially, maybe it >increments if a child dies and is restarted?). It would be helpful if >it listed the real process ID for the child (at least in addition), >not some PID internal to the server. > >It might be difficult to make happen, but it would be really, really >nice if you could kill and spawn children on the fly. For example, >right now I'm running 12 children, but it looks like I could >definitely handle more. I have to either kill all 12 or start a new >parent. > >I don't know how much you want to expand the basic functionality of >the parent's netcon rather than let people write their own tools, but >some things like a way to do a "say" on each child (sayall "Servers >shutting down soon!") or a way see a specific child's status/stats >would be helpful. Maybe even instead of having each child have a >netcon (or in addition), you can do "connect <child ID>" in the parent >netcon and it'd context switch between them as if you connected to >that specific server. >Actually, I spoke too soon. Using netcon for a child is broken for >me. I can run commands (and they work), but I get no responses back >from the server on the netcon connection. I can see the responses in >the parent's console, though. I've used the shutdown command a few times for testing and brought the servers back up, but strangely, I only got the failed assertion message the very first time. I still don't get any output from the children through netcon. I've since upped the forks to 16 (plus a mostly-empty TF2 server) and haven't had any issues on our Q6600 with only 2 gigs of RAM. The only other thing is if you forget you're looking at the parent console (not netcon) and try to enter commands, it'll all get dumped into your shell when your parent finally terminates. It would be nice if the parent console would just silently eat all input, if not take the same input as the parent netcon does. -Fyren _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
