Quote
*snip*
- Fixed a case where servers could have "ghost" players consuming player slots.
*snip*
And in addition to those changes, we have made large changes in the Linux engine, moving to a newer compiler, adding multiple GCC specific optimizations and changing the filesystem layout for binaries to match more closely to other platforms builds.
These changes have a few consequences you should be aware of. We have increased the minimum glibc version to 2.3.6, our survey shows that over 95% of you already have newer glibc's so this shouldn't generally be an issue. The new compiler and optimizations has also changed the binary format, if you are using tools that do binary patches into our engine (SourceMod and the like) then these will no longer function, the authors of those products will need to provide updates to get them working again. We have also increased our usage of threads and mutex constructs, if you see hangs or deadlocks on your server (when you didn't before) a gdb backtrace of the process will help us pin down problem.
Jason (Valve)
- Fixed a case where servers could have "ghost" players consuming player slots.
*snip*
And in addition to those changes, we have made large changes in the Linux engine, moving to a newer compiler, adding multiple GCC specific optimizations and changing the filesystem layout for binaries to match more closely to other platforms builds.
These changes have a few consequences you should be aware of. We have increased the minimum glibc version to 2.3.6, our survey shows that over 95% of you already have newer glibc's so this shouldn't generally be an issue. The new compiler and optimizations has also changed the binary format, if you are using tools that do binary patches into our engine (SourceMod and the like) then these will no longer function, the authors of those products will need to provide updates to get them working again. We have also increased our usage of threads and mutex constructs, if you see hangs or deadlocks on your server (when you didn't before) a gdb backtrace of the process will help us pin down problem.
Jason (Valve)
Linux gets optimizations? I guess a bunch of server admins just sold their souls to the devil in order to get this (Also Mac support helped).
EDIT:
In addition, it might take a little while for the servers to update. Valve's content servers are on dialup:
Quote
Updating Installation
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Updating 'Team Fortress 2 Content' from version 139 to version 141
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Updating 'Team Fortress 2 Content' from version 139 to version 141
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Updating 'Team Fortress 2 Content' from version 139 to version 141
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Retrying in 30 seconds. . .
Updating 'Team Fortress 2 Content' from version 139 to version 141

Help



MultiQuote









