Srcds.exe is widely used in what I would deem "serious" game hosting operations and yet this application really hasn't evolved much beyond the level of a consumer product. I expect many administrators who are supporting srcds in such environments would agree that it presents some operational management challenges.
What I think might be useful, perhaps in future srcds versions, would be the inclusion of more a few management features that would make it a more robust application in a hosting environment: 1. Some Application Event logging - with informative events backed up by some kind of knowledge base that would help operators determine root causes that are within their scope of control. 2. Some application instrumentation (E.g. PerfMon counters, WMI hooks) that could be used to better monitor application performance and state and employ mainstream third party management tools. 3. A version that runs as a true Windows service, that responds correctly and gracefully to Service Manager actions (Start, Stop, Pause). My $.02 F. P.S. And a "headshot" tag in the kill event in the DOD:S game log :) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roman Hatsiev Sent: Wednesday, April 26, 2006 4:13 AM To: [email protected] Subject: Re: [hlds] SRCDS Mini Dump Files This is true unless you have source code and debugging symbols which may give you a clue where it crashed. Even those won't help you much if you are ot familiar with software internals.... On 26/04/06, Stuart Stegall <[EMAIL PROTECTED]> wrote: > For the most part debuggers don't really provide anything helpful and > are generally a crutch. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
