[hlds_linux] Counter-Strike: Source Beta release
We have just released an update to Counter-Strike: Source Beta. You need to run hldsupdatetool to get this update. This release fixes a problem with long commands causing the server to generate an error and exit. - Alfred ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Segmentation fault on Fedora 2
thanks for the suggestion, we've set them to pingboost 1 just now and will see if it helps overnight (though we've been running fine with pingboost 3 set for ages, and we've got 3 other servers all using same settings with no issues right now - just different flavours of linux) - I'll let you know how we get on tomorrow, I'm willing to try anything at the moment. cheers, Steve Perhaps you could use +pingboost 1 or or just remove the +pingboost flag and see if that helps... Just my $.02. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Segmentation fault on Fedora 2
That is correct. - Original Message - From: "kama" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 07, 2004 08:30 AM Subject: Re: [hlds_linux] Segmentation fault on Fedora 2 > > isnt it -pingboost and not +pingboost??? > > /Bjorn ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Segmentation fault on Fedora 2
isnt it -pingboost and not +pingboost??? /Bjorn On Tue, 7 Sep 2004, TJ Hilton wrote: > Um it's my understanding that using the pingboost settings can mess stuff up. > > Below is the explanation of the pingboost flag for linux. I've found > this same description in many places around the net. I can't say who > originated the message, just that I've seen the same text a lot so > perhaps it has some validity. > > "Mode "1" reduces latency by using a different wait method (a select() > call). This method reduces the latency to 10msec. > > Mode "2" uses a similar but slightly different method (and alarm() > type call). Again, the result it 10msec worth of latency being added. > NOTE that this method has the potential to hang a server in certain > (terminal) situations. > > Mode "3" minimises the latency to the minimum possible level by > processing a frame EVERY time a packet arrives. This causes the lowest > possible latency, but can also cause extreme CPU usages (it does a > complete frame for every packet, with each player sending lots of > packets per second and 30 players this adds up to insane amounts of > frames). Use this mode at your own risk, it will consume all available > CPU. In a future release this mode will be tweaked to let the admin > balance latencies agains CPU usage (by processing a frame every N > packets). " > > Perhaps you could use +pingboost 1 or or just remove the +pingboost > flag and see if that helps... > > Just my $.02. > > > On Tue, 7 Sep 2004 02:21:53 +0100, RippED <[EMAIL PROTECTED]> wrote: > > Hi there, > > > > Hope someone can help me, or let me know where to go for some help (can we > > email a Valve support email direct somewhere?). We did a steam update about > > 3 weeks ago, and ever since we've been receiving complaints of CS servers > > restarting when players join - server OS is Fedora 2 (Linux version > > 2.6.5-1.358smp - Red Hat Linux 3.3.3-7). Sure enough when I checked it out, > > and used the -debug option I note that there are 3-4 core files being > > produced per day, and the servers are fairly empty at the moment. > > > > There are two CS servers running on this box, one with adminmod/metamod and > > the other totally default installation (no mods or plugins) - both give same > > errors with a slight variance in the memory address that the fault occurs > > within; therefore I'm thinking that this can't be to do with the installed > > plugins, but is more likely a core hlds issue or incompatibility with > > something in fedora 2 (perhaps a library version problem?). > > > > We use the following as startup script, in case it matters:- > > #!/bin/sh > > #/var/servers/starthosted1.sh > > export LD_LIBRARY_PATH=/var/servers/hosted1 > > cd $LD_LIBRARY_PATH > > screen -dmS hosted1 ./hlds_run -game cstrike +map de_dust2 +sys_ticrate 600 > > +pingboost 3 +maxplayers 13 +ip xx.xxx.xxx.xx +port 27025 -autoupdate -debug > > &2> /dev/null > > > > here is the -debug generated debug.log content:- > > -- > > CRASH: Tue Sep 7 00:45:34 BST 2004 > > Start Line: ./hlds_i686 -game cstrike +map de_dust2 +sys_ticrate 600 > > +pingboost > > 3 +maxplayers 13 +ip 82.138.247.21 +port 27025 -autoupdate -debug -pidfile > > hlds. > > 1749.pid > > Using host libthread_db library "/lib/tls/libthread_db.so.1". > > Core was generated by `./hlds_i686 -game cstrike +map de_dust2 +sys_ticrate > > 600 > > +pingboost 3 +maxplaye'. > > Program terminated with signal 11, Segmentation fault. > > #0 0x55264d41 in ?? () > > #0 0x55264d41 in ?? () > > End of crash report > > -- > > > > here is the output we received from execution of gdb on one of the core > > files:- > > $ gdb hlds_i686 core.2041 > > GNU gdb Red Hat Linux (6.0post-0.20040223.19rh) > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain > > conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db > > library "/lib/tls/libthread_db.so.1". > > > > Core was generated by `./hlds_i686 -game cstrike +map de_dust2 +sys_ticrate > > 600 +pingboost 3 +maxplaye'. > > Program terminated with signal 11, . > > Cannot access memory at address 0x55004000 > > #0 0x55264d41 in ?? () > > (gdb) bt > > #0 0x55264d41 in ?? () > > Cannot access memory at address 0xfefe9220 > > (gdb) info locals > > No symbol table info available. > > (gdb) info sharedlibrary > > Cannot access memory at address 0x55004000 > > (gdb) info frame > > Stack level 0, frame at 0xfefe9224: > > eip = 0x55264d41; saved eip Cannot access memory at address 0xfefe9220 > > (gdb) quit > > $ > > > > Any help you folks could give would be most appreciated. > > Thanks for reading > > - Stev
Re: [hlds_linux] Segmentation fault on Fedora 2
Um it's my understanding that using the pingboost settings can mess stuff up. Below is the explanation of the pingboost flag for linux. I've found this same description in many places around the net. I can't say who originated the message, just that I've seen the same text a lot so perhaps it has some validity. "Mode "1" reduces latency by using a different wait method (a select() call). This method reduces the latency to 10msec. Mode "2" uses a similar but slightly different method (and alarm() type call). Again, the result it 10msec worth of latency being added. NOTE that this method has the potential to hang a server in certain (terminal) situations. Mode "3" minimises the latency to the minimum possible level by processing a frame EVERY time a packet arrives. This causes the lowest possible latency, but can also cause extreme CPU usages (it does a complete frame for every packet, with each player sending lots of packets per second and 30 players this adds up to insane amounts of frames). Use this mode at your own risk, it will consume all available CPU. In a future release this mode will be tweaked to let the admin balance latencies agains CPU usage (by processing a frame every N packets). " Perhaps you could use +pingboost 1 or or just remove the +pingboost flag and see if that helps... Just my $.02. On Tue, 7 Sep 2004 02:21:53 +0100, RippED <[EMAIL PROTECTED]> wrote: > Hi there, > > Hope someone can help me, or let me know where to go for some help (can we > email a Valve support email direct somewhere?). We did a steam update about > 3 weeks ago, and ever since we've been receiving complaints of CS servers > restarting when players join - server OS is Fedora 2 (Linux version > 2.6.5-1.358smp - Red Hat Linux 3.3.3-7). Sure enough when I checked it out, > and used the -debug option I note that there are 3-4 core files being > produced per day, and the servers are fairly empty at the moment. > > There are two CS servers running on this box, one with adminmod/metamod and > the other totally default installation (no mods or plugins) - both give same > errors with a slight variance in the memory address that the fault occurs > within; therefore I'm thinking that this can't be to do with the installed > plugins, but is more likely a core hlds issue or incompatibility with > something in fedora 2 (perhaps a library version problem?). > > We use the following as startup script, in case it matters:- > #!/bin/sh > #/var/servers/starthosted1.sh > export LD_LIBRARY_PATH=/var/servers/hosted1 > cd $LD_LIBRARY_PATH > screen -dmS hosted1 ./hlds_run -game cstrike +map de_dust2 +sys_ticrate 600 > +pingboost 3 +maxplayers 13 +ip xx.xxx.xxx.xx +port 27025 -autoupdate -debug > &2> /dev/null > > here is the -debug generated debug.log content:- > -- > CRASH: Tue Sep 7 00:45:34 BST 2004 > Start Line: ./hlds_i686 -game cstrike +map de_dust2 +sys_ticrate 600 > +pingboost > 3 +maxplayers 13 +ip 82.138.247.21 +port 27025 -autoupdate -debug -pidfile > hlds. > 1749.pid > Using host libthread_db library "/lib/tls/libthread_db.so.1". > Core was generated by `./hlds_i686 -game cstrike +map de_dust2 +sys_ticrate > 600 > +pingboost 3 +maxplaye'. > Program terminated with signal 11, Segmentation fault. > #0 0x55264d41 in ?? () > #0 0x55264d41 in ?? () > End of crash report > -- > > here is the output we received from execution of gdb on one of the core > files:- > $ gdb hlds_i686 core.2041 > GNU gdb Red Hat Linux (6.0post-0.20040223.19rh) > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db > library "/lib/tls/libthread_db.so.1". > > Core was generated by `./hlds_i686 -game cstrike +map de_dust2 +sys_ticrate > 600 +pingboost 3 +maxplaye'. > Program terminated with signal 11, . > Cannot access memory at address 0x55004000 > #0 0x55264d41 in ?? () > (gdb) bt > #0 0x55264d41 in ?? () > Cannot access memory at address 0xfefe9220 > (gdb) info locals > No symbol table info available. > (gdb) info sharedlibrary > Cannot access memory at address 0x55004000 > (gdb) info frame > Stack level 0, frame at 0xfefe9224: > eip = 0x55264d41; saved eip Cannot access memory at address 0xfefe9220 > (gdb) quit > $ > > Any help you folks could give would be most appreciated. > Thanks for reading > - Steve > > ___ > To unsubscribe, edit your list preferences, or view the list archives, please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > -- TJ Hilton [EMAIL PROTECTED] ___ To unsubscribe,
Re: [hlds_linux] HLDS on FreeBSD?
FreeBSD will run HLDS and HLDS Src also. Provided that you have installed linux-base-8 from ports. That port containes the proper glib component. I'm running both of my servers off of FreeBSD 4.10 currently. -- Micheal Patterson - Original Message - From: "CAL-Account" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 06, 2004 11:21 PM Subject: [hlds_linux] HLDS on FreeBSD? Hi guys: I've been wanting to install HLDS on a FreeBSD 4.10 system and from what I can gather, the HLDS is for Linux and Windows only. What would I have to do to get it to work correctly under FreeBSD 4.10? Thanks. Rob ___ 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
