well, replay crashed the server before, even if not enabled, so don't say that too loud.....
>________________________________ >From: ics <[email protected]> >To: Half-Life dedicated Linux server mailing list ><[email protected]> >Sent: Wednesday, 27 July 2011, 17:45 >Subject: Re: [hlds_linux] Team Fortress 2 Update Released > >I said wrong before, i ment we have 4 servers and 2 of them had crashed >after the latest update. Also I refuse to annoy players with weapon or >class limitations. > >There are now less crashes than before but ultimately Valve should fix >the cause. I don't run bots or run replay on the servers so that's not >the issue for crashes either. > >-ics > >27.7.2011 18:20, Aaron "DJ Zyrphon" Thompson kirjoitti: >> Ics: All of my crashes have been either related to the new laser weapons or >> the mantreads...usually the mantreads. There is a SourceMod plugin called >> Unlock Replacer that I modified to block the Mantreads while they (Valve) >> work out the kinks. >> >> Go to the last post and download my files and the unlock.games.txt somewhere >> in the middle of the thread (another page other than 1 or 18) and install >> the three files. In your sourcemod.cfg file add this line: >> >> sm_unlock_block "Mantreads" >> >> It didn't work before but as of the update it seems to be working. >> Sent from my MOTOBLUR™ smartphone on AT&T >> >> -----Original message----- >> From: ics<[email protected]> >> To: Half-Life dedicated Linux server mailing >> list<[email protected]> >> Sent: Wed, Jul 27, 2011 14:34:06 GMT+00:00 >> Subject: Re: [hlds_linux] Team Fortress 2 Update Released >> >> I'm having crashes. 4 so far on 2 of our TF2 servers. Luckily they seem >> to reboot themselves back up now so i don't need to restart them.. yet. >> >> -ics >> >> 27.7.2011 16:49, AnAkIn . kirjoitti: >>> Had a crash today too. Might be replay related as the function it crashed in >>> is bot related. There are no other bots on the server. >>> >>> 2011/7/27 clad iron<[email protected]> >>> >>>> Is there a possibility of valve adding cvars for each weapon to disable 1 >>>> at >>>> a time ? >>>> This way if problems arise with them , they could be disabled , or if >>>> server >>>> op's do not want certain weapons on the server. >>>> >>>> On Wed, Jul 27, 2011 at 9:40 AM, Chris<[email protected]> wrote: >>>> >>>>> I disabled the new weapons a few days ago on my server and haven't >>>>> experienced any crashes since. >>>>> I'm wondering with the recent update if anyone is experiencing crashing >>>>> still? I'd like to re-enable these weapons if everything seems to be >>>>> functioning without any problems. >>>>> >>>>> Let me know. >>>>> >>>>> Chris >>>>> >>>>> On Wed, Jul 27, 2011 at 7:58 AM, Bajdechi "Nightbox" Alexandru< >>>>> [email protected]> wrote: >>>>> >>>>>> I had a crash few minutes ago, anyone still have problems ? >>>>>> >>>>>> PS: Valve reopened their servers ? I see matchmaking fails to deliver >>>>>> players to servers in my region. >>>>>> >>>>>> 2011/7/27 Zover Mirklo<[email protected]> >>>>>> >>>>>>> Just had a hang on cp_egypt_final. It started using all the 100% of >>>>>>> core of cpu and I couldnt even detach the screen. I am probably >>>>>>> going to block new weapons.This is the second time it happens. On >>>>>>> first time it hanged all my box. Only manual box restart helped.. >>>>>>> Citējot *Jesse Molina<[email protected]> [1]*: >>>>>>>> I use a bash srcds control script that does the following before a >>>>>>>> quit; >>>>>>>> >>>>>>>> STOPCOUNTDOWN=10 >>>>>>>> until [ $STOPCOUNTDOWN -eq 0 ] ; do >>>>>>>> echo -n "." >>>>>>>> # Send both a say and cm_csay, since sm_csay requires sourcemod. >>>>>>>> tmux send-keys -t $GAMEDIR >>>>>>>> "sm_csay Server is shutting down in $STOPCOUNTDOWN seconds!" C-m >>>>>>>> tmux send-keys -t $GAMEDIR >>>>>>>> "say Server is shutting down in $STOPCOUNTDOWN seconds!" C-m >>>>>>>> STOPCOUNTDOWN=$(( $STOPCOUNTDOWN - 1)) >>>>>>>> sleep 1 >>>>>>>> done >>>>>>>> tmux send-keys -t $GAMEDIR "quit" C-m >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I use tmux instead of screen, but you can probably do the same >>>> with >>>>>>>> screen. This does not require rcon, though that would be an >>>>>>>> alternative >>>>>>>> method of sending the commands. >>>>>>>> >>>>>>>> Also, if you use the "quit" command (exit also works/does the same >>>>>>>> thing?) then the clients don't time-out. They get a packet which >>>>>>>> triggers a nice dialog box, which tells them that the server is >>>>>>>> shutting >>>>>>>> down, similar to if they had been kicked. >>>>>>>> >>>>>>>> Depending upon the reason for the shutdown, you could control the >>>>>>>> message sent in the say/sm_say commands via another $variable. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Comments welcome. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> E3pO wrote: >>>>>>>> > is there a good way to warn the server that there is an update >>>>>>>> and needs to >>>>>>>> > restart instead of just restarting the server and saying "WE >>>>>>>> ARE GOING TO >>>>>>>> > RESTART FOR UPDATES" like a million times? >>>>>>>> > >>>>>>>> > When you kill the server players clients time out and then get >>>>>>>> a lost >>>>>>>> > connection to server. It would be cool to have someth >> _______________________________________________ >> 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
