Don't be so quick on the trigger, srcds is a big program that takes in a
tremendous amount of hard to guess data and has to run on a large
variety of hardware and OSs. Testing this stuff isn't exactly
straightforward.
Also, does anyone have high use Tf2 beta servers running? Do customers
even pay for beta servers?
On 7/21/2011 7:08 AM, E3pO wrote:
Whoever has the final call on releasing updates needs to be fired. It is
illogical to release an update for such a widely used application without
testing and then just walk away from the update station and go to sleep.
Hell, i'm willing to bet it was about 85% done uploading to the content
servers about to release the update and the guy just called it a night.
And what the hell are they doing so different each time that breaks so many
things?
Added the items for Dr. Grordbort's Victory Pack
- Fixed hatless hats not working correctly
- Fixed a display issue with team color paints
- Updated the localization files
So how many hats have they released now? You would think they would have
that figured out by now. They fixed a display issue, seems like that is
client side and not related to the server.. and updated localization files?
What does any of that have anything to do with the server crashing? Is there
some kind of offication change log we can have access to so we know what has
been modified? Maybe a more in depth update info instead of just "Added some
items". That update did much more then that..
And I still don't see why Valve bothered making a TF2 BETA if they don't
even use it.
Make code changes and document the changes, build, test test test test test
test test test and test more, then have someone else look over the code and
say "Oh hell that will cause a buffer overflow if you have to many sentries!
change that to this.." then fix and test test test test more and have more
people look into it and once all the code changes have been reviewed and
locked down send an email to the list telling everyone what has been changed
and that there will be an update available in 1 hour of the email. make a
build for TF2 BETA and update preferably sometime in the morning hours so
that stuff doesn't break while you're sleeping and you wake up to broken
servers.
Keep an eye out and check statistics for how many servers are running and
how many are updating and how many have crashed after the update etc. Keep
an eye on the list and after a few days of absolutely NO problems with the
new build warn the TF2 server admins that it will be released 12 PM EST (or
w\e time) so they can be prepared.
Isn't that just common sense? Who the hell would build an artificial heart
for their father and just give it to him without testing it out first. Hell
he may of forgot battery.c
On Thu, Jul 21, 2011 at 6:37 AM, Mart-Jan Reeuwijk<mreeu...@yahoo.com>wrote:
Oh, don't you know? its for having a stable game... and if memory serves me
well, it doesn't even crash.
________________________________
From: E3pO<e...@wmclan.net>
To: Half-Life dedicated Linux server mailing list<
hlds_linux@list.valvesoftware.com>
Sent: Thursday, 21 July 2011, 8:21
Subject: Re: [hlds_linux] Server crashes after today's update
Valve, quick question.
What is Team Fortress 2 Beta for?
kthxbai.
On Thu, Jul 21, 2011 at 12:38 AM, Tony Paloma<drunkenf...@hotmail.com
wrote:
Yes I crashed again
*** glibc detected *** ./srcds_linux: double free or corruption (!prev):
0x1aeae148 ***
The double free makes more sense.
*snip*
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
