Yes using real-time can causes props to malfunctionProps start having conflicts when calling on the clock time/ing/ers , while competing for CPU time a bit more is involved but that's the boiled down idea of what is happening. Lorne M.aka. BlyteDate: Mon, 30 Jul 2012 06:41:00 -0700 From: [email protected] To: [email protected] Subject: Re: [hlds] Handling server crashes the smart way
Interesting. I'm running SRCDS on RT in Linux and occasionally props will be missing on a map, doors won't open and the cart will sometimes stop moving. Could this be the cause of it (Not trying to hijack the thread, just curious) On Mon, Jul 30, 2012 at 5:23 AM, Lorne Mock <[email protected]> wrote: correction Setting on high can cause all kinds of strange things to happen should read Setting on real-time can cause all kinds of strange things to happen need to proof read my posts a little better ... sorry From: [email protected] To: [email protected] Date: Mon, 30 Jul 2012 07:17:34 -0500 Subject: Re: [hlds] Handling server crashes the smart way The only thing I notice is the cpu process priority. It should be set no greater than high. If set on real-time priority the process will be competing for CPU time with the system/hardware drivers Setting on high can cause all kinds of strange things to happen, like driver corruption and HDD faults to name a few. This is most likely the reason Windows becomes unstable. Set it above-normal or high never on real-time priority. Hope this helps clear things up for you. Lorne M. aka Blyte Date: Sun, 29 Jul 2012 16:19:22 -0300 From: [email protected] To: [email protected] Subject: [hlds] Handling server crashes the smart way Hello, I'm running a CS: S server on a windows 2003 server computer. I know that it's outdated, and windows is highly unstable at times, but I've been getting a lot of server crashes for the last two weeks and with each crash comes a dump file. These dump files don't appear to hold many information about the crash, pretty useless to me. But they must be there for a reason. So I was wondering if there's a 'smart' way to "pin-point" at what instance the srcds crashed. I'll leave some dox about the server that I'm running, maybe you'll find something 'un-usual' Windows 2003 Server Counter-Strike: Source dedicated server Running process with all cpus (process affinity) Running on RealTime priority (might change it to High) Addons: Mani Admin System Mattie's Eventscripts DAF DoS Fix (Blocks flood of server queries to the server) Any help is appreciated _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
