--
[ Picked text/plain from multipart/alternative ]
The only thing that I could think of that would cause that would be if the
server is crashing, which is logical then that the PID changes.
Matt Ogborne <[EMAIL PROTECTED]> wrote: --
[ Picked text/plain from multipart/alternative ]
Howdy,
Long t
--
[ Picked text/plain from multipart/alternative ]
Howdy,
Long time reader, first post, so pls be gentle :-)
Until recently the PID (process ID) for a CS:S server running used to stay
the same, thus using taskset in Linux, we were able to set the process to
run on a specific CPU core.
However r
As to what exactly the problem is I don't recall a definitive answer.. but
yes for the time being your P3 and some (allot) of the AMD cpu's are out of
luck. I ended up building a new system with an Xeon E5335 (was running a LAN
server with an athlon XP2800) and life is good again.
--kennycom
Quick run-down:
1. Reports surface that the Orange Box SrcDS (OBSrcDS from here on)
fails on older processors.
2. Circumstantial evidence is shown that lack of SSE2 might lead to
these errors.
3. Chris Green (Valve) states that SSE2 is not required (only plain SSE,
available on P3s, is) as no com
--
[ Picked text/plain from multipart/alternative ]
Hey All,
So I have a P3 linux server I run CS:S on and thought i'd dedicate it to TF2,
read through some of the old postings to his mailing list and it looks like the
P3 doesn't support some processor function the newer TF2 engine needs in orde
I'll have to play with my server a bit if you haven't figured it out
already. I set it up at 66 tick so I haven't tried pushing it past
that.
On 11/5/07, Theo Macris <[EMAIL PROTECTED]> wrote:
> --
> [ Picked text/plain from multipart/alternative ]
> It never goes above 68. My settings are 100/100
Well, that does make more sense than mine.
Leave it to me to make things overcomplicated :D
Keeper
___
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:hlds_linux-
> [EMAIL PROTECTED] On Behalf Of ics
> Sent: Tuesday, November 06, 2007 10:20 AM
> To: hlds_linux@list.valvesoftware.com
> Subject: Re: [hlds_linux] 24/7 servers and map reloads...
>
> mp_timelimit 0
>
> Map never changes or
I am writing an admin plugin that is 100% pure, no hacks. It doesn't have
any flash and dazzle, but will be a fully functional stable admin plugin
when finished.
I want to make sure that it works with the Linux version of TF2 before I go
into full beta release, but this will work on all orange box
mp_timelimit 0
Map never changes or reloads again. No timelimit, no map changes.
-ics
Miano, Steven M. kirjoitti:
--
[ Picked text/plain from multipart/alternative ]
I am attempting to set up a 24/7 dustbowl server for Team Fortress 2, and it
seems to be running well, however each time a roun
My Suggestion ( don't know if this will work )
mp_timelimit "20"
mp_bonusroundtime "15"
mp_restartgame "1214" //20 minutes 14 seconds
Maybe I'm wrong, but the game should restart 1 second before the map tries
to reload.
I haven't played much with TF2 yet, but in theory this should work.
Keeper
--
[ Picked text/plain from multipart/alternative ]
I am attempting to set up a 24/7 dustbowl server for Team Fortress 2, and it
seems to be running well, however each time a round ends, it reloads the map.
I've seen on other servers that they don't need to reload the map, and simply
reset the s
12 matches
Mail list logo
