[hlds_linux] Re: [hlds] Request to clear steam id's from global ban lists
A review of our ban list turned up some steamid's that should not be banned. If you are using the global ban list from http://70.85.25.116/banned_user.txt then please take the time to remove the following accounts from your banned_user.cfg: STEAM_0:1:6555719 STEAM_0:1:4973968 STEAM_0:1:1123940 STEAM_0:1:4284202 STEAM_0:0:4167326 STEAM_0:0:3277947 STEAM_0:1:5453208 STEAM_0:0:4379225 STEAM_0:1:5289314 STEAM_0:0:3320503 STEAM_0:1:5332537 STEAM_0:1:4912823 STEAM_0:1:1716825 STEAM_0:1:988502 STEAM_0:1:5860323 Here is the same set prefixed with the removeid command for easy running on your server(s): removeid STEAM_0:1:4973968 removeid STEAM_0:1:1123940 removeid STEAM_0:1:4284202 removeid STEAM_0:0:4167326 removeid STEAM_0:0:3277947 removeid STEAM_0:1:5453208 removeid STEAM_0:0:4379225 removeid STEAM_0:1:5289314 removeid STEAM_0:0:3320503 removeid STEAM_0:1:5332537 removeid STEAM_0:1:4912823 removeid STEAM_0:1:1716825 removeid STEAM_0:1:988502 removeid STEAM_0:1:5860323 Thank you. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
--On Thursday, April 07, 2005 11:41 PM +0200 Thiesson Johann <[EMAIL PROTECTED]> wrote: That's just voodoo networking. Select a port because it "feels" right (presumably because of reading some bare-bones howto), lacking any understanding of the technology. You see this as server admin. But the customer, or even simply the player, would not understand why his server port is not as 95% of the other servers, between 27000 and 27100. Perhaps, but you can add the explanation of why it's not so to a FAQ. Plenty of "how it works" documents around the Internet that can be referenced. Once you leave the safety of a default port for a service, it doesn't really matter how far away you get. You still have to enter a value, and a value far away might be easier to get right than one nearby, because the customer won't as easily assume that the value you gave him is "wrong" and correct it to the default value. Now if Valve (and other game makers) started supporting SRV records, you could eliminate ports from the UI and just use names. But's that pie in the sky, considering how few services have support for SRV. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
- Original Message - From: "ScratchMonkey" <[EMAIL PROTECTED]> Related question: If the desired port is unavailable, should the binary still try to grab the next one available, or hard-fail? I'd prefer the latter, because I'd want to know if the port moved, and not have it silently shift around due to some unrelated phenomenon. But for some that might mean a middle-of-the-night call when a server mysteriously goes down. Perhaps another config parameter to select the failure mode is called for. Agreed, not so critical for none "public ports" but for game ports and query ports having them stay put is critical. Steve / K This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
Steven Hartland wrote: Indeed all port MUST be able to be to be explicitly specified otherwise by by servers. It not feasible to have one port randomly assign itself BETA or not people should know by now, need another port create config param for it, the two should be one. You should know by now that messing things up is the valve way to test features that should be inside and working from the begining. As alfred put it eloquently - "dumb luck" but I'm afraid that it is not luck who's dumb. -- Mariusz Zielinski ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
-- On Apr 07, 14:03, ScratchMonkey wrote: > --On Thursday, April 07, 2005 3:50 PM -0400 Michael McKoy <[EMAIL PROTECTED]> > wrote: > > >They like to use the default port or a similar port, evidenced by the > >fact that there's thousands of servers on ports 27016-27030, etc. > > That's just voodoo networking. Select a port because it "feels" right > (presumably because of reading some bare-bones howto), lacking any > understanding of the technology. You see this as server admin. But the customer, or even simply the player, would not understand why his server port is not as 95% of the other servers, between 27000 and 27100. Other thing, I'm afraid with some changes by valve, like this 27030 binded port. And I would not be surprised if one day they decide to force the port range to 270__ for example... My servers configurations are as "common" as possible, I feel better like this. (This is off-topic, but my actual fear is the future CPU needs for VAC2. Valve love to make surprises :) -- Thiesson Johann -- Content-Description: Digital signature [ signature.asc of type application/pgp-signature deleted ] -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
--On Thursday, April 07, 2005 10:08 PM +0100 Steven Hartland <[EMAIL PROTECTED]> wrote: Indeed all port MUST be able to be to be explicitly specified otherwise by by servers. It not feasible to have one port randomly assign itself BETA or not people should know by now, need another port create config param for it, the two should be one. Absolutely! Related question: If the desired port is unavailable, should the binary still try to grab the next one available, or hard-fail? I'd prefer the latter, because I'd want to know if the port moved, and not have it silently shift around due to some unrelated phenomenon. But for some that might mean a middle-of-the-night call when a server mysteriously goes down. Perhaps another config parameter to select the failure mode is called for. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
Indeed all port MUST be able to be to be explicitly specified otherwise by by servers. It not feasible to have one port randomly assign itself BETA or not people should know by now, need another port create config param for it, the two should be one. Steve / K - Original Message - From: "Justin McCarter" <[EMAIL PROTECTED]> Michael - IMO, you hit it right on the head. The VAC2 port binding has great potential for overlap with the main listen port for existing servers, especially for those of us with many servers. All ports that are bound by the srcds/hlds server processes we should be able to explicitly specify. This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
--On Thursday, April 07, 2005 3:50 PM -0400 Michael McKoy <[EMAIL PROTECTED]> wrote: They like to use the default port or a similar port, evidenced by the fact that there's thousands of servers on ports 27016-27030, etc. That's just voodoo networking. Select a port because it "feels" right (presumably because of reading some bare-bones howto), lacking any understanding of the technology. As another person posted to the list, they had over 90 customers on port 27030. VAC2 has disrupted their business and forced them to move these customers. That's a reasonable objection, based on continuity of service. A bunch of you seem hell bent on bashing me for a bad choice of words in my first post No more bashing than when my compiler tells me I've made a syntax error. That's not the compiler "bashing" me. It's telling me I screwed up, and it's right in doing so. One of the reasons end users adhere to voodoo is because of conflicting information arising from erroneous posts like yours. If one doesn't correct the error, the voodoo continues. Sorry if it sounds like I'm bashing you. I just don't want incorrect information to spread, because that creates support headaches for all of us down the road. I often have to figure out where some end user picked up some lore, so I can figure out if the lore had a real foundation in the idiosyncrasies of some implementation or is just poor wording from some engineer. (The worst kind of voodoo is voodoo programming, where one finds something hideous and uncommented in source code, written by a long-departed programmer, and doesn't know if it's safe to rewrite because it might be coded that way due to some compiler issue or some weird hardware dependency.) ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
Hear hear! (Is that the right homonym to use here?) Michael - IMO, you hit it right on the head. The VAC2 port binding has great potential for overlap with the main listen port for existing servers, especially for those of us with many servers. All ports that are bound by the srcds/hlds server processes we should be able to explicitly specify. -Justin On Apr 7, 2005 1:50 PM, Michael McKoy <[EMAIL PROTECTED]> wrote: > > You've missed the point then. Yes. There is no technical reason you can't > put it on port 1000, 5, 16969, whatever you want. The point is that IN > PRACTICE, most people do NOT do that nor have a desire to do so. They like > to use the default port or a similar port, evidenced by the fact that > there's thousands of servers on ports 27016-27030, etc. > > My point has never been that there is a technical reason you couldn't use > any port you want. My point was simply that most people, though in > particular game server providers, traditionally use ports starting at > 27015 and up. As another person posted to the list, they had over 90 > customers on port 27030. VAC2 has disrupted their business and forced them > to move these customers. > > A bunch of you seem hell bent on bashing me for a bad choice of words in > my first post, which I tried to correct, while ignoring the issue I tried > to get addressed: > > VAC2 binds itself to 0.0.0.0:27030 and there's no way for us to change > that, and it has affected many people's server setups. It should obey the > -ip parameter, and perhaps even a -vac2port parameter. > > > ___ > 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] Segmentation errors on Source
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] Hi, Source update causing segmentation errors? After the latest Source update, I was unable to start the Source server and got "segmentation errors". When I deleted the blob file and updated again, the problem was solved and the Source server was started without errors. This morning the complete server didn't respond anymore to commands (webmin, SSH, steam, ..), but I performed PING's and got a responds. I rebooted (the hard way) and have currently disabled the Source server until I figure out what is causing this. The machine (2gig ECC enabled memory, mirrored disks, dual AMD, sufficient cooling) was recently (January) installed again with Slackware 10 and caused no problem until now. Debug.log CRASH: Thu Apr 7 10:20:52 CEST 2005 Start Line: ./srcds_amd -game cstrike +ip x +maxplayers 18 +map de_dust -debug Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `./srcds_amd -game cstrike +ip xxx +maxplayers 18 +map de_dust -debug'. Program terminated with signal 11, Segmentation fault. #0 0x404bdac4 in ?? () #0 0x404bdac4 in ?? () End of Source crash report Server output: L 04/07/2005 - 22:22:17: "Gary<3>" joined team "TERRORIST" L 04/07/2005 - 22:22:17: World triggered "Game_Commencing" L 04/07/2005 - 22:22:17: "Gary<3><>" entered the game ./srcds_run: line 426: 17118 Segmentation fault (core dumped) $HL_CMD Cannot access memory at address 0x40014f7c debug.cmds:1: Error in sourced command file: Cannot access memory at address 0xbfffc6ec email debug.log to [EMAIL PROTECTED] Thu Apr 7 22:22:17 CEST 2005: Server restart in 10 seconds Has anybody seen this error before and how was it solved? The day before I changed playercount from 18 to 32 with custom maps. Could this in any way be related ? Any ideas, suggestions, ideas, .. All are welcome. Thanks. Tom Briers Aka. Cybernavy -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
>> Taking into consideration that in practice, people aren't going to put >> a CSS server on port 8000 or 43000. In general, most people cluster >> around 27015 and up. The way things are now, you only have up to 27019 >> before you run into the 27020 port from the first server on 27015. >> (And at that point, ports 27021 to 27024 are also in use) > > There's no reason I can't put my game servers on arbitrary ports above > 1024, even with a wealth of non-game services running. A CS server runs > perfectly fine on port 12345 and 54321. (I'm assuming the client, > server, and master server programs aren't broken in some way that > prevents them from doing what any other program can do.) You've missed the point then. Yes. There is no technical reason you can't put it on port 1000, 5, 16969, whatever you want. The point is that IN PRACTICE, most people do NOT do that nor have a desire to do so. They like to use the default port or a similar port, evidenced by the fact that there's thousands of servers on ports 27016-27030, etc. My point has never been that there is a technical reason you couldn't use any port you want. My point was simply that most people, though in particular game server providers, traditionally use ports starting at 27015 and up. As another person posted to the list, they had over 90 customers on port 27030. VAC2 has disrupted their business and forced them to move these customers. A bunch of you seem hell bent on bashing me for a bad choice of words in my first post, which I tried to correct, while ignoring the issue I tried to get addressed: VAC2 binds itself to 0.0.0.0:27030 and there's no way for us to change that, and it has affected many people's server setups. It should obey the -ip parameter, and perhaps even a -vac2port parameter. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
--On Thursday, April 07, 2005 2:36 AM -0500 "Eric (Deacon)" <[EMAIL PROTECTED]> wrote: That's a bit like saying, "What? You complain about traffic congestion during your morning commute? Yeah, with only MILLIONS of miles of open road to choose from, I can see how your 15 mile stretch would limit you." In reality, there are not 64k worth of really/practically usable ports, as explained in a previous email by someone else. I musta misssed that explanation. Or are you referring to this: Taking into consideration that in practice, people aren't going to put a CSS server on port 8000 or 43000. In general, most people cluster around 27015 and up. The way things are now, you only have up to 27019 before you run into the 27020 port from the first server on 27015. (And at that point, ports 27021 to 27024 are also in use) There's no reason I can't put my game servers on arbitrary ports above 1024, even with a wealth of non-game services running. A CS server runs perfectly fine on port 12345 and 54321. (I'm assuming the client, server, and master server programs aren't broken in some way that prevents them from doing what any other program can do.) ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
You can run the same amount of servers on one IP but on different ports or on multiple IPs witht the same IP. You could run a server on port 1000, 2000, 3000, etc. and the server won't complain, as long as another service is not using the port. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Counter-Strike: Source and Source Engine update
In a bold display of creativity, ScratchMonkey wrote: Yeah, with only 64,000 ports to choose from, I can see how 4 UDP ports per server would limit you! ;) That's a bit like saying, "What? You complain about traffic congestion during your morning commute? Yeah, with only MILLIONS of miles of open road to choose from, I can see how your 15 mile stretch would limit you." In reality, there are not 64k worth of really/practically usable ports, as explained in a previous email by someone else. -- Eric (the Deacon remix) ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux