The Linux dedicated server for Team Fortress 2 has been updated again.
This update fixes the Assertion Failure: ValidationServerIP1 !=
ValidationServerIP2 that some servers were getting.
Jason
___
To unsubscribe, edit your list preferences, or view th
A required update to Team Fortress 2 and it's dedicated server have been
released. Please run hldsupdatetool to update. The specific changes
include:
Team Fortress 2:
- Sudden Death mode is now a server option (a convar) and defaults to
OFF
- Sapped buildings now take slightly less damage from t
The actual priority and the niced priority are different. The priority changes
all the time, while the niced value is used to force it to a certain level.
Make sure you're reading the niced column. Tasks using CPU will generally have
a lower value (lower number = higher priority) than ones not d
the lower the priority the more "important" the process in regards to CPU
time (which allows it to get cpu time above other processes), you can
specify this with a command line argument (nice or renice once it is
running) i don't know of any hard coded scheduling present in the srcds
process, typi
--
[ Picked text/plain from multipart/alternative ]
This is good news. I just found this crash in my console log, good to know
it's at least being looked into. :) Here's my message:
DebugAssert
Expr: pValidationContext->m_u32UserIDTicketValidationServerIPAddr2 !=
pValidationContext->m_u32UserID
--
[ Picked text/plain from multipart/alternative ]
Seems that srcds_i486 process is started with priority -3 . Is it ok?
Cause strange but all other processes (for example cs 1.6 servers)
are started with priority 20. Is the priority -3 set automatically by
srcds_i486? Or something is wrong with m
6 matches
Mail list logo
