RT is for almost any application "not recommended". Lorne Mock is right on
that.
Just set the SRCDS's on High, and put anything else on "low" prio. (except
maybe that firewall you have on)
>________________________________
> From: Essay Tew Phaun <[email protected]>
>To: Half-Life dedicated Win32 server mailing list
><[email protected]>
>Sent: Monday, 30 July 2012, 15:41
>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
