RE: [hlds_linux] Half-Life 1 Deathmatch and Team Fortress Classic Updated
Make sure you correctly updated your server. You can use the "-verify_all" flag to double check this. - Alfred Dan Offord wrote: > -- > [ Picked text/plain from multipart/alternative ] > Jason: > > This issue still isn't fixed. I was still able to crash a server > using the > same exploit. > > Dan. > > On 23/04/07, Jason Ruymen <[EMAIL PROTECTED]> wrote: >> >> Updates to Half-Life 1 Deathmatch and Team Fortress Classic have been >> released. Please run hldsupdatetool to download these updates. The >> specific changes include: >> >> - Fixed game server crash when lastinv was inappropriately used >> >> Jason >> >> >> ___ >> To unsubscribe, edit your list preferences, or view the list >> archives, please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> > > > > -- > .: =CATS= Gaming :. > .: http://www.catsgaming.com :. > .: This email contains information that maybe confidential if your > not the > intended recipient, please delete this email :. > -- > > ___ > 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
Re: [hlds_linux] Problems running SRCDS and HLDS at the same server
For source, you are still missing some ports. Try the below startup line format: ./srcds_run -game cstrike +ip 123.123.123.123 -port 27015 \ -clientport 27005 -steamport 27009 -tv_port 27020 +map de_dust2 \ +maxplayers 20 -tickrate 100 Yes it is -steamport for source, not -sport. At least this is how it was communicated by Valve. You can verify which ports are in use by which process, by typing: netstat -nlutp Or if you like, use the (shameless plug) startup script I created for this: http://www.livebythegun.com/forum/about541.html Feed it the argument "ports" and it will return which ports are in use for that particular script. As for CS 1.6.. No idea what the command line arguments are.. Sorry, can't help you there. The netstat -nlutp will at least show you which ports the process has in use though. Have fun! --- Regime http://www.livebythegun.com Andreas Kang Schøyen wrote: > # 27017 SRDCS > > cd /home/cs/steam/27017; > > screen -Sdm css_27017 ./srcds_27017 -game cstrike +port 27017 -sport 27041 > +tv_port 27050 +map de_dust2 +maxplayers 20 -tickrate 100 -secure > +mp_dynamicpricing 0 -autoupdate +ip 80.90.242.77 > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Half-Life 1 Deathmatch and Team Fortress Classic Updated
-- [ Picked text/plain from multipart/alternative ] Jason: This issue still isn't fixed. I was still able to crash a server using the same exploit. Dan. On 23/04/07, Jason Ruymen <[EMAIL PROTECTED]> wrote: > > Updates to Half-Life 1 Deathmatch and Team Fortress Classic have been > released. Please run hldsupdatetool to download these updates. The > specific changes include: > > - Fixed game server crash when lastinv was inappropriately used > > Jason > > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > -- .: =CATS= Gaming :. .: http://www.catsgaming.com :. .: This email contains information that maybe confidential if your not the intended recipient, please delete this email :. -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Still CSS Problems
Hi: Try kernel 2.6.21.rc7 and enable dynamic ticks and high timer options. Now my fps are more stable on 1.6 and source. With kernel 2.6.20 i get big drops(80). Specs: Debian 4.0 etch kernel: custom 2.6.21.rc7(enabled dynamic ticks and high timers with 1000 hz) Intel Core 2 Duo 6600 4GB DDR2 It seems to be related with multicore, because same config on p4 work perfect. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Still CSS Problems
-- [ Picked text/plain from multipart/alternative ] On Windows we gave up and just made all our servers 18 & 20 player servers On 4/24/07, Arne Guski <[EMAIL PROTECTED]> wrote: > > This is a multi-part message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > As it became quiet around this problem, i would also like to point out > that this issue is far from beeing resolved. > > I state again: > We run all-Intel-CPUs from P4s over dual / quad xeons to core 2 duos, > all with nearly the exact lag issues. > All running Debian almost the same problems on Sarge and Etch (now > running Etch since its stable) > All running cut down Preemt Kernels with 1000Hz (2.6.16.40+), also tried > countless other Versions including 2.6.20 and 2.6.21-rc7 with / without > dyntick, different IO Schedulers ... so everything that could cause > problems is sorted out from our side. > Since these boxes are dedicated for gameservers only there is not much > else on them besides proftpd-mysql, snmpd and our webinterface-backend > (really just some perl scripts croned) that could cause any trouble. > > Problems are almost identical with the current "public" version and the > beta, therefore our customer servers are still running on build 2949, as > everything else is performing far from what our customers expect. > > I agree with TC from UKCS, that valve should put some focus on > optimizing performance, but then ... they have not thought about that a > single second in the last 2 year .. so basically i have given up hope on > that one ... > > I do hope this issue will get resolved soon ... as there might be a > point where we will be unable to use the "working" build (caused by some > client update or whatnot) and therefore beeing unable to offer source > servers to our customers. > > Arne Guski > www.server-sales.de > Forum: http://forum.server-sales.de > Qnet: #server-sales.de > Mail: [EMAIL PROTECTED] > ICQ: 48395948 > > > > > > Message: 3 > > From: "Michael Shavit" <[EMAIL PROTECTED]> > > To: > > Subject: RE: [hlds_linux] Still CSS Problems > > Date: Mon, 23 Apr 2007 20:22:49 +0200 > > Organization: Binarics GmbH > > Reply-To: hlds_linux@list.valvesoftware.com > > > > Hello, > > > > I would like to add here too from our side, we still have fps drops and > > latency increase even with the betaupdate, on Debian as also RedHat. > Hope > > Valve is still taking care of that. > > > > Cheers, > > Michael > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Tobias > Rehn > > Sent: Montag, 23. April 2007 13:19 > > To: hlds_linux@list.valvesoftware.com > > Subject: [hlds_linux] Still CSS Problems > > > > Hey, > > > > We tested several configurations (Debian unstable, testing, stable + > > different kernels + different hw [Intel <-> AMD]) the last weeks and > > there still seem to be these enormous fps drops in css. There is no > > difference between the beta binaries and the originals. Does anyone have > > a fix for this? > > > > I already tested debian unstable because of the new glibc (2.5). But > > there is still some loss of performance according to the server versions > > before the last update. It runs much better with this version but still > > its not as good as before the server update 1 1/2 weeks ago. > > > > Kind regards, Tobias Rehn > > > > ___ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > > > > > > > > > > > --__--__-- > > > > Message: 6 > > From: "TC" <[EMAIL PROTECTED]> > > To: > > Cc: <[EMAIL PROTECTED]> > > Subject: RE: [hlds_linux] Still CSS Problems > > Date: Mon, 23 Apr 2007 21:39:07 +0100 > > Reply-To: hlds_linux@list.valvesoftware.com > > > > The srcds0407 source beta engine causes terrible lag problems at the > start > > of rounds on a full server and had to be backed off all my machines. It > > better not be included as a mandatory change in the next release as that > > would be disastrous. If Valve insists on that change they need to make > it > > optional controlled by a cvar, not forced on everyone. > > > > It is unclear to me why they started changing that part of the code to > > attempt a fix the problem in the beta, when it doesn't sound like that > was > > the area they had previously fiddled with. Valve shouldn't be changing > code > > to try to fix something in an area of the code they hadn't touched when > they > > broke it. That is only shifting the sands and in this case introduces > new > > problems for different people. > > > > I have to admit I have been fortunate not to have suffered from any of > the > > lag problems reported through this forum except from the beta srcds0407. > I > > run a mixture of operating systems on various boxes, both 32 bit and 64 > bit, > > AMD and Intel, single and multi processor and various kernel versions. I > use > > glib2.3.6 by de
RE: [hlds_linux] Problems running SRCDS and HLDS at the same server
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] # 27015 HLDS cd /home/cs/steam/27015/ screen -Sdm cs_27015 ./run27015 -game cstrike -console +port 27015 -sport 27040 +maxplayers 32 +map de_dust2 -secure -pingboost 2 -autoupdate +ip 80.90.242.77 sleep 60 screen -S cs_27015 -X -p0 eval "stuff 'restart'^m" > /dev/null 2>&1 sleep 1 # 27037 HLDS cd /home/cs/steam/27037/ screen -Sdm cs_27037 ./run27037 -game cstrike -console +port 27037 -sport 27044 +maxplayers 17 +map de_dust2 -secure -autoupdate +ip 80.90.242.77 sleep 60 screen -S cs_27037 -X -p0 eval "stuff 'restart'^m" > /dev/null 2>&1 sleep 1 # 27017 SRDCS cd /home/cs/steam/27017; screen -Sdm css_27017 ./srcds_27017 -game cstrike +port 27017 -sport 27041 +tv_port 27050 +map de_dust2 +maxplayers 20 -tickrate 100 -secure +mp_dynamicpricing 0 -autoupdate +ip 80.90.242.77 sleep 60 # 27018 SRCDS cd /home/cs/steam/27018; screen -Sdm css_27018 ./srcds_27018 -game cstrike +port 27018 -sport 27042 +tv_port 27051 +map cs_office +maxplayers 20 -tickrate 100 -secure +mp_dynamicpricing 0 -autoupdate +ip 80.90.242.77 sleep 60 # 27019 SRCDS cd /home/cs/steam/27019; screen -Sdm css_27019 ./srcds_27019 -game cstrike +port 27019 -sport 27043 +tv_port 27052 +map cs_office +maxplayers 20 -tickrate 100 -secure +mp_dynamicpricing 0 -autoupdate +ip 80.90.242.77 sleep 60 # 27036 SRCDS cd /home/cs/steam/27036; screen -Sdm css_27036 ./srcds_27036 -game cstrike +port 27036 -sport 27045 +tv_port 27053 +map cs_office +maxplayers 16 -tickrate 66 -secure +mp_dyna This looks ok? Med vennlig hilsen: Andreas Kang Schøyen It konsulent NovaNett AS Adr: Grønland 14, 0188 Oslo E-post: [EMAIL PROTECTED] Tlf: 22170020 / Mob 9699 Faks: 22178218 Web: www.novanett.no -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Ottalini Sent: Tuesday, April 24, 2007 11:32 AM To: hlds_linux@list.valvesoftware.com Subject: Re: [hlds_linux] Problems running SRCDS and HLDS at the same server I've found that the order in which you start up the HL1 and HL2 servers is extremely important, depending especially on how you specify ports in the launch properties. 1. It's always important to launch servers with the target port in the launch properties, although on an all SRCDS servers they will auto search for a free port if one is taken, it's still best to make sure that they all launch on their intended port (keeps your regulars a lot happier too). 2. Start all servers in incrementing port sequence (this seems to help keep things clean). 3. Never start all servers at once, always start servers 30 to 60 seconds apart, at the very minimum wait until they successfully log onto the steam servers. 4. all servers should have unique -sport specified (VAC port) - you can skip specifying this you only run HL2 servers but if you mix and match it's very important to specify them. 5. make sure for SRCDS servers that the port is open for TCP as well as UDP in the firewall/router if you want RCON to work 6. Ideally, all HLDS services must be restarted at least once before you start a server on the next port ... don't ask me why but all HLDS servers that haven't been restarted at least once are sure to act strangely and starting the next server when the previous one hasn't been restarted may well also start acting weird. This is one setup I find work the best for me: a. SRCDS on port 27015 should be started first with -port 27015 -sport 26902 in the launch properties b. HLDS on port 27016 should be started second with -port 27016 -sport 26904 in the launch properties On my linux server, If I start HLDS first, then one or more SRCDS processes this seems to work ok without specifying the -sport, but if I start an SRCDS and then an HLDS server, HLDS gets very confused and will act weird. I mostly believe that the problem here is SRCDS will look for ports it needs and if they are not available it will automatically try the next in sequence, but HLDS is not able to search at all and instead of complaining that it's unable to acquire a needed port it just stalls there. Just a last gotcha note, if you have to shut down the HLDS server and restart it (or it crashes, etc) you may find that weirdness will return when it restarts again in a system with SRCDS servers already running. Specifying both ports appears to help this, but the HLDS server must be restarted at least once to get it clean. (By restart I mean in HLDS issuing the "restart" command or any changelevel ) - Original Message - From: "Andreas Kang Schøyen" To: Sent: Tuesday, April 24, 2007 12:41 AM Subject: [hlds_linux] Problems running SRCDS and HLDS at the same server Are there any known issues to run HLDS and SRCDS at the same server? I have bought a "super server" capable of running many servers, but I have met some error
RE: [hlds_linux] Problems running SRCDS and HLDS at the same server
Thanks, just a few thing.. How do I send the restart command to the server with my startup script? And you post -port isn't it +port for srcds? Med vennlig hilsen: Andreas Kang Schøyen It konsulent NovaNett AS Adr: Grønland 14, 0188 Oslo E-post: [EMAIL PROTECTED] Tlf: 22170020 / Mob 9699 Faks: 22178218 Web: www.novanett.no -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Ottalini Sent: Tuesday, April 24, 2007 11:32 AM To: hlds_linux@list.valvesoftware.com Subject: Re: [hlds_linux] Problems running SRCDS and HLDS at the same server I've found that the order in which you start up the HL1 and HL2 servers is extremely important, depending especially on how you specify ports in the launch properties. 1. It's always important to launch servers with the target port in the launch properties, although on an all SRCDS servers they will auto search for a free port if one is taken, it's still best to make sure that they all launch on their intended port (keeps your regulars a lot happier too). 2. Start all servers in incrementing port sequence (this seems to help keep things clean). 3. Never start all servers at once, always start servers 30 to 60 seconds apart, at the very minimum wait until they successfully log onto the steam servers. 4. all servers should have unique -sport specified (VAC port) - you can skip specifying this you only run HL2 servers but if you mix and match it's very important to specify them. 5. make sure for SRCDS servers that the port is open for TCP as well as UDP in the firewall/router if you want RCON to work 6. Ideally, all HLDS services must be restarted at least once before you start a server on the next port ... don't ask me why but all HLDS servers that haven't been restarted at least once are sure to act strangely and starting the next server when the previous one hasn't been restarted may well also start acting weird. This is one setup I find work the best for me: a. SRCDS on port 27015 should be started first with -port 27015 -sport 26902 in the launch properties b. HLDS on port 27016 should be started second with -port 27016 -sport 26904 in the launch properties On my linux server, If I start HLDS first, then one or more SRCDS processes this seems to work ok without specifying the -sport, but if I start an SRCDS and then an HLDS server, HLDS gets very confused and will act weird. I mostly believe that the problem here is SRCDS will look for ports it needs and if they are not available it will automatically try the next in sequence, but HLDS is not able to search at all and instead of complaining that it's unable to acquire a needed port it just stalls there. Just a last gotcha note, if you have to shut down the HLDS server and restart it (or it crashes, etc) you may find that weirdness will return when it restarts again in a system with SRCDS servers already running. Specifying both ports appears to help this, but the HLDS server must be restarted at least once to get it clean. (By restart I mean in HLDS issuing the "restart" command or any changelevel ) - Original Message - From: "Andreas Kang Schøyen" To: Sent: Tuesday, April 24, 2007 12:41 AM Subject: [hlds_linux] Problems running SRCDS and HLDS at the same server Are there any known issues to run HLDS and SRCDS at the same server? I have bought a "super server" capable of running many servers, but I have met some errors along the way. It seems that the SRCDS interfere with the Steam Validation for hlds? Sometimes the hlds servers can't validate steamids and all the new players get steamid pending. And for the source servers.. they just get offline and no error message is printed to the console for the server. I have learned that SRCDS uses port 27020 -> for source TV and that's why I run hlds on port 27015-27019 and SRCDS on ports 27035-> The server has extern IP and all ports that HLDS and VAC need are opened up. Maybe get another IP to the server and run hlds on eth0 and srcds on eth0:1 ? Anyone? ___ 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
RE: [hlds_linux] Still CSS Problems
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] As it became quiet around this problem, i would also like to point out that this issue is far from beeing resolved. I state again: We run all-Intel-CPUs from P4s over dual / quad xeons to core 2 duos, all with nearly the exact lag issues. All running Debian almost the same problems on Sarge and Etch (now running Etch since its stable) All running cut down Preemt Kernels with 1000Hz (2.6.16.40+), also tried countless other Versions including 2.6.20 and 2.6.21-rc7 with / without dyntick, different IO Schedulers ... so everything that could cause problems is sorted out from our side. Since these boxes are dedicated for gameservers only there is not much else on them besides proftpd-mysql, snmpd and our webinterface-backend (really just some perl scripts croned) that could cause any trouble. Problems are almost identical with the current "public" version and the beta, therefore our customer servers are still running on build 2949, as everything else is performing far from what our customers expect. I agree with TC from UKCS, that valve should put some focus on optimizing performance, but then ... they have not thought about that a single second in the last 2 year .. so basically i have given up hope on that one ... I do hope this issue will get resolved soon ... as there might be a point where we will be unable to use the "working" build (caused by some client update or whatnot) and therefore beeing unable to offer source servers to our customers. Arne Guski www.server-sales.de Forum: http://forum.server-sales.de Qnet: #server-sales.de Mail: [EMAIL PROTECTED] ICQ: 48395948 > Message: 3 > From: "Michael Shavit" <[EMAIL PROTECTED]> > To: > Subject: RE: [hlds_linux] Still CSS Problems > Date: Mon, 23 Apr 2007 20:22:49 +0200 > Organization: Binarics GmbH > Reply-To: hlds_linux@list.valvesoftware.com > > Hello, > > I would like to add here too from our side, we still have fps drops and > latency increase even with the betaupdate, on Debian as also RedHat. Hope > Valve is still taking care of that. > > Cheers, > Michael > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tobias Rehn > Sent: Montag, 23. April 2007 13:19 > To: hlds_linux@list.valvesoftware.com > Subject: [hlds_linux] Still CSS Problems > > Hey, > > We tested several configurations (Debian unstable, testing, stable + > different kernels + different hw [Intel <-> AMD]) the last weeks and > there still seem to be these enormous fps drops in css. There is no > difference between the beta binaries and the originals. Does anyone have > a fix for this? > > I already tested debian unstable because of the new glibc (2.5). But > there is still some loss of performance according to the server versions > before the last update. It runs much better with this version but still > its not as good as before the server update 1 1/2 weeks ago. > > Kind regards, Tobias Rehn > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > > > > --__--__-- > > Message: 6 > From: "TC" <[EMAIL PROTECTED]> > To: > Cc: <[EMAIL PROTECTED]> > Subject: RE: [hlds_linux] Still CSS Problems > Date: Mon, 23 Apr 2007 21:39:07 +0100 > Reply-To: hlds_linux@list.valvesoftware.com > > The srcds0407 source beta engine causes terrible lag problems at the start > of rounds on a full server and had to be backed off all my machines. It > better not be included as a mandatory change in the next release as that > would be disastrous. If Valve insists on that change they need to make it > optional controlled by a cvar, not forced on everyone. > > It is unclear to me why they started changing that part of the code to > attempt a fix the problem in the beta, when it doesn't sound like that was > the area they had previously fiddled with. Valve shouldn't be changing code > to try to fix something in an area of the code they hadn't touched when they > broke it. That is only shifting the sands and in this case introduces new > problems for different people. > > I have to admit I have been fortunate not to have suffered from any of the > lag problems reported through this forum except from the beta srcds0407. I > run a mixture of operating systems on various boxes, both 32 bit and 64 bit, > AMD and Intel, single and multi processor and various kernel versions. I use > glib2.3.6 by default and also tried glib2.5 but have been unable to > re-create the problem on any combination. > > The fact that it doesn't affect everybody makes it sound like they have done > something in the code that can now upset the operating system. If it was > something basic it would be in the main valve code and affect everybody. > Maybe they updated their compiler version or used different compile > switches, or added a rogue system c
Re: [hlds_linux] Problems running SRCDS and HLDS at the same server
I've found that the order in which you start up the HL1 and HL2 servers is extremely important, depending especially on how you specify ports in the launch properties. 1. It's always important to launch servers with the target port in the launch properties, although on an all SRCDS servers they will auto search for a free port if one is taken, it's still best to make sure that they all launch on their intended port (keeps your regulars a lot happier too). 2. Start all servers in incrementing port sequence (this seems to help keep things clean). 3. Never start all servers at once, always start servers 30 to 60 seconds apart, at the very minimum wait until they successfully log onto the steam servers. 4. all servers should have unique -sport specified (VAC port) - you can skip specifying this you only run HL2 servers but if you mix and match it's very important to specify them. 5. make sure for SRCDS servers that the port is open for TCP as well as UDP in the firewall/router if you want RCON to work 6. Ideally, all HLDS services must be restarted at least once before you start a server on the next port ... don't ask me why but all HLDS servers that haven't been restarted at least once are sure to act strangely and starting the next server when the previous one hasn't been restarted may well also start acting weird. This is one setup I find work the best for me: a. SRCDS on port 27015 should be started first with -port 27015 -sport 26902 in the launch properties b. HLDS on port 27016 should be started second with -port 27016 -sport 26904 in the launch properties On my linux server, If I start HLDS first, then one or more SRCDS processes this seems to work ok without specifying the -sport, but if I start an SRCDS and then an HLDS server, HLDS gets very confused and will act weird. I mostly believe that the problem here is SRCDS will look for ports it needs and if they are not available it will automatically try the next in sequence, but HLDS is not able to search at all and instead of complaining that it's unable to acquire a needed port it just stalls there. Just a last gotcha note, if you have to shut down the HLDS server and restart it (or it crashes, etc) you may find that weirdness will return when it restarts again in a system with SRCDS servers already running. Specifying both ports appears to help this, but the HLDS server must be restarted at least once to get it clean. (By restart I mean in HLDS issuing the "restart" command or any changelevel ) - Original Message - From: "Andreas Kang Schøyen" To: Sent: Tuesday, April 24, 2007 12:41 AM Subject: [hlds_linux] Problems running SRCDS and HLDS at the same server Are there any known issues to run HLDS and SRCDS at the same server? I have bought a "super server" capable of running many servers, but I have met some errors along the way. It seems that the SRCDS interfere with the Steam Validation for hlds? Sometimes the hlds servers can't validate steamids and all the new players get steamid pending. And for the source servers.. they just get offline and no error message is printed to the console for the server. I have learned that SRCDS uses port 27020 -> for source TV and that's why I run hlds on port 27015-27019 and SRCDS on ports 27035-> The server has extern IP and all ports that HLDS and VAC need are opened up. Maybe get another IP to the server and run hlds on eth0 and srcds on eth0:1 ? Anyone? ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
RE: [hlds_linux] Problems running SRCDS and HLDS at the same server
Thanks the sport is that for hlds aswell? Med vennlig hilsen: Andreas Kang Schøyen It konsulent NovaNett AS Adr: Grønland 14, 0188 Oslo E-post: [EMAIL PROTECTED] Tlf: 22170020 / Mob 9699 Faks: 22178218 Web: www.novanett.no -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gavin Rodgers Sent: Tuesday, April 24, 2007 11:05 AM To: hlds_linux@list.valvesoftware.com Subject: RE: [hlds_linux] Problems running SRCDS and HLDS at the same server You may want to force the ports +port -sport +tv_port Eg +port 27015 -sport 27016 For source add something like +tv_port 27017 So for a second server you may do +port 27020 -sport 27021 and if its source +tv_port 27022 See if that helps. Gavin Rodgers (BlueHawk^4u) 4u-servers.co.uk 4u-servers.co.uk/forums (forums, now with 500+ FREE arcade games) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Kang Schøyen Sent: 24 April 2007 08:42 To: hlds_linux@list.valvesoftware.com Subject: [hlds_linux] Problems running SRCDS and HLDS at the same server Are there any known issues to run HLDS and SRCDS at the same server? I have bought a "super server" capable of running many servers, but I have met some errors along the way. It seems that the SRCDS interfere with the Steam Validation for hlds? Sometimes the hlds servers can't validate steamids and all the new players get steamid pending. And for the source servers.. they just get offline and no error message is printed to the console for the server. I have learned that SRCDS uses port 27020 -> for source TV and that's why I run hlds on port 27015-27019 and SRCDS on ports 27035-> The server has extern IP and all ports that HLDS and VAC need are opened up. Maybe get another IP to the server and run hlds on eth0 and srcds on eth0:1 ? Anyone? ___ 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
RE: [hlds_linux] Problems running SRCDS and HLDS at the same server
You may want to force the ports +port -sport +tv_port Eg +port 27015 -sport 27016 For source add something like +tv_port 27017 So for a second server you may do +port 27020 -sport 27021 and if its source +tv_port 27022 See if that helps. Gavin Rodgers (BlueHawk^4u) 4u-servers.co.uk 4u-servers.co.uk/forums (forums, now with 500+ FREE arcade games) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Kang Schøyen Sent: 24 April 2007 08:42 To: hlds_linux@list.valvesoftware.com Subject: [hlds_linux] Problems running SRCDS and HLDS at the same server Are there any known issues to run HLDS and SRCDS at the same server? I have bought a "super server" capable of running many servers, but I have met some errors along the way. It seems that the SRCDS interfere with the Steam Validation for hlds? Sometimes the hlds servers can't validate steamids and all the new players get steamid pending. And for the source servers.. they just get offline and no error message is printed to the console for the server. I have learned that SRCDS uses port 27020 -> for source TV and that's why I run hlds on port 27015-27019 and SRCDS on ports 27035-> The server has extern IP and all ports that HLDS and VAC need are opened up. Maybe get another IP to the server and run hlds on eth0 and srcds on eth0:1 ? Anyone? ___ 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
Re: [hlds_linux] 1.6 FPS drops
I removed the SMT and multi core scheduler support from the kernel and the FPS seems to be more stable now. Another thing i noticed is that disabling ACPI seems to limit performance. 23 apr 2007 kl. 22.27 skrev Jonathan Selander: Doesn't that just taskset the shell which executes the script? Or does it apply to other processes executed from the script as well? I tried it a couple of hours ago but didn't notice any difference in performance. Svensk Ljud & Ljus Produktion skrev: I have a script to lanch the server and iI did add this " taskset - c 0 ./srcds_run ." Peter - Original Message - From: "Jonathan" <[EMAIL PROTECTED]> To: Sent: Monday, April 23, 2007 6:35 PM Subject: Re: [hlds_linux] 1.6 FPS drops Was that using tasket? Did you modify hlds_run to launch it using taskset or how did you do? have you tried to bind the running server to only one core ? I did that yesterday, and it works better.. peter - Original Message - From: "Jonathan" <[EMAIL PROTECTED]> To: Sent: Monday, April 23, 2007 1:35 PM Subject: [hlds_linux] 1.6 FPS drops Hi, I've created a new kernel with the 2.6.21-rc6 using the dynamic ticks and high timer options, which really improved the performance of my server. I need to run the servers at 1000 FPS because it appeals to customers. The hardware is dual quad-core xeon 2.66ghz with 8gb fully-buffered memory. The FPS is generally at 980-1000, but sometimes it drops to around 500. This happens with only one, completely idle server running on the machine. Perhaps i don't need to care about this, but i'd really like to know what can cause these drops to happen? Apparently the CPU is able to keep it at a steady 1000 FPS, and since there's nothing else running i don't see why it should drop to ~500. ___ 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 ___ 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
[hlds_linux] Problems running SRCDS and HLDS at the same server
Are there any known issues to run HLDS and SRCDS at the same server? I have bought a "super server" capable of running many servers, but I have met some errors along the way. It seems that the SRCDS interfere with the Steam Validation for hlds? Sometimes the hlds servers can't validate steamids and all the new players get steamid pending. And for the source servers.. they just get offline and no error message is printed to the console for the server. I have learned that SRCDS uses port 27020 -> for source TV and that's why I run hlds on port 27015-27019 and SRCDS on ports 27035-> The server has extern IP and all ports that HLDS and VAC need are opened up. Maybe get another IP to the server and run hlds on eth0 and srcds on eth0:1 ? Anyone? ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
