[GH-ISSUE #96] A few suggestions for l4d2server script #73

Closed
opened 2026-02-27 01:59:22 +03:00 by kerem · 4 comments
Owner

Originally created by @patriotgames on GitHub (Jun 20, 2014).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/96

Originally assigned to: @dgibbs64 on GitHub.

Daniel,

Again, thank you for sharing your excellent scripts.

I would like to share a couple of modifications that I use in your l4d2server script. These are easily done by anyone, but some users may prefer to have them included rather than attempting to modify the script. Perhaps you might think about incorporating these in a future update:

  1. Remove "sourcetvport=" from Start Variables and remove "+tv_port ${sourcetvport}" from fn_parms as this service is not functional with l4d2.
  2. Add "rconpassword=" to Start Variables and add "+rcon_password ${rconpassword}" to fn_parms as part of the server launch parameters. Change "rcon=$(grep -s rcon_password "${servercfgfullpath}"|sed 's/rcon_password //g'|sed 's/"//g')" in Server Details to "rcon="${rconpassword}"" It is more secure to set rcon password in the server launch line than in the server.cfg, and you don't have to parse the password from the file.
  3. Add "otherparms=" to Start Variables and add "${otherparms}" to fn_parms as part of the server launch parameters. This allows for easily adding additional non-standard or test parameters to the server launch line. Example:
    otherparms="-debug +allow_all_bot_survivor_team 1"

Finally, and this is very optional, for those users who wish to use processor affinity for their server the following can be added to the server script:

  1. Add "cpuaffinity=" to Start Variables and change the following line in fn_startserver to include tasket:

tmux new-session -d -s ${servicename} "taskset -c ${cpuaffinity} ${executable} ${parms}|tee -a '${consolelog}'"

"cpuaffinity" is the core number (typically 0-7 on an 8-core processor) to which the user wants to assign the server. After testing on my l4d2 servers, I have opted not to assign individual srcds instances to specific processor cores (the server has 8). However, implementing processor affinity for other games or engines may be beneficial.

Cheers,
Patriot

Originally created by @patriotgames on GitHub (Jun 20, 2014). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/96 Originally assigned to: @dgibbs64 on GitHub. Daniel, Again, thank you for sharing your excellent scripts. I would like to share a couple of modifications that I use in your l4d2server script. These are easily done by anyone, but some users may prefer to have them included rather than attempting to modify the script. Perhaps you might think about incorporating these in a future update: 1. Remove "sourcetvport=" from Start Variables and remove "+tv_port ${sourcetvport}" from fn_parms as this service is not functional with l4d2. 2. Add "rconpassword=" to Start Variables and add "+rcon_password ${rconpassword}" to fn_parms as part of the server launch parameters. Change "rcon=$(grep -s rcon_password "${servercfgfullpath}"|sed 's/rcon_password //g'|sed 's/"//g')" in Server Details to "rcon="${rconpassword}"" It is more secure to set rcon password in the server launch line than in the server.cfg, and you don't have to parse the password from the file. 3. Add "otherparms=" to Start Variables and add "${otherparms}" to fn_parms as part of the server launch parameters. This allows for easily adding additional non-standard or test parameters to the server launch line. Example: otherparms="-debug +allow_all_bot_survivor_team 1" Finally, and this is very optional, for those users who wish to use processor affinity for their server the following can be added to the server script: 1. Add "cpuaffinity=" to Start Variables and change the following line in fn_startserver to include tasket: tmux new-session -d -s ${servicename} "taskset -c ${cpuaffinity} ${executable} ${parms}|tee -a '${consolelog}'" "cpuaffinity" is the core number (typically 0-7 on an 8-core processor) to which the user wants to assign the server. After testing on my l4d2 servers, I have opted not to assign individual srcds instances to specific processor cores (the server has 8). However, implementing processor affinity for other games or engines may be beneficial. Cheers, Patriot
kerem 2026-02-27 01:59:22 +03:00
Author
Owner

@dgibbs64 commented on GitHub (Jun 21, 2014):

Some great suggestions here I will look at implementing some of these as part of the next release. I would like to find out the best parms for the other servers as well as I know that some vary. Cpu affinity would be a great feature to implement. Thanks for the suggestions.

<!-- gh-comment-id:46749191 --> @dgibbs64 commented on GitHub (Jun 21, 2014): Some great suggestions here I will look at implementing some of these as part of the next release. I would like to find out the best parms for the other servers as well as I know that some vary. Cpu affinity would be a great feature to implement. Thanks for the suggestions.
Author
Owner

@dgibbs64 commented on GitHub (Jun 21, 2014):

Point one I am implementing in next release

Point two. Do you have any articles etc to back this up as this would be a major change and cause me quite a bit of work. Also having a password in the parms I believe would mean it shows in clear text on the process list (ps -ef). Allowing other users on the server to see the rcon password for that server.

Point 3. Parms is designed for people to customize how they want already. I only set default parameters that people will probably use or are important for the script. It is easy enough to just add extra parameters to to end of parms.

I want to implement cpu affinity but don't know much about it. I believe this would be beneficial to some users. What is the default for using all cores by default? and could the user assign multiple cores? some examples

cpuaffinity="2"
cpuaffinity="1 2"
cpuaffinity="all"

Thanks :)

<!-- gh-comment-id:46753688 --> @dgibbs64 commented on GitHub (Jun 21, 2014): Point one I am implementing in next release Point two. Do you have any articles etc to back this up as this would be a major change and cause me quite a bit of work. Also having a password in the parms I believe would mean it shows in clear text on the process list (ps -ef). Allowing other users on the server to see the rcon password for that server. Point 3. Parms is designed for people to customize how they want already. I only set default parameters that people will probably use or are important for the script. It is easy enough to just add extra parameters to to end of parms. I want to implement cpu affinity but don't know much about it. I believe this would be beneficial to some users. What is the default for using all cores by default? and could the user assign multiple cores? some examples cpuaffinity="2" cpuaffinity="1 2" cpuaffinity="all" Thanks :)
Author
Owner

@twinsuns commented on GitHub (Aug 3, 2014):

I for one would like to also set cpu affinity for my TF2 servers. I will edit the script for now but it would be great to see an official release.

<!-- gh-comment-id:51007466 --> @twinsuns commented on GitHub (Aug 3, 2014): I for one would like to also set cpu affinity for my TF2 servers. I will edit the script for now but it would be great to see an official release.
Author
Owner

@lock[bot] commented on GitHub (Jul 20, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:406479859 --> @lock[bot] commented on GitHub (Jul 20, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No labels
Atomic
Epic
cannot reproduce
command: backup
command: console
command: debug
command: details
command: fast-dl
command: install
command: mods
command: monitor
command: post-details
command: restart
command: send
command: start
command: stop
command: update
command: update-lgsm
command: validate
command: wipe
distro: AlmaLinux
distro: Arch Linux
distro: CentOS
distro: Debian
distro: Fedora
distro: RedHat
distro: Rocky Linux
distro: Ubuntu
distro: openSUSE
engine: goldsrc
engine: source
game: 7 Days to Die
game: ARMA 3
game: Ark: Survival Evolved
game: Assetto Corsa
game: Avorion
game: BATTALION: Legacy
game: Barotrauma
game: Battalion 1944
game: Battlefield 1942
game: Black Mesa: Deathmatch
game: Blade Symphony
game: Call of Duty 2
game: Call of Duty 4
game: Call of Duty: United Offensive
game: Counter-Strike 1.6
game: Counter-Strike 2
game: Counter-Strike: Global Offensive
game: Counter-Strike: Source
game: Day of Infamy
game: Dayz
game: Death Match Classic
game: Don't Starve Together
game: ET: Legacy
game: Eco
game: Factorio
game: Factorio
game: Garry's Mod
game: Half-Life
game: Hurtword
game: Insurgecy
game: Insurgecy
game: Insurgency: Sandstorm
game: Just Cause 3
game: Killing Floor
game: Killing Floor 2
game: Left 4 Dead 2
game: Minecraft
game: Minecraft Bedrock
game: Mordhau
game: Multi Theft Auto
game: Mumble
game: Natural Selection 2
game: No More Room in Hell
game: Pavlov VR
game: Post Scriptum
game: Project Zomboid
game: Quake 3
game: QuakeWorld
game: Red Orchestra: Ostfront 41-45
game: Return to Castle Wolfenstein
game: Rising World
game: Rust
game: San Andreas Multiplayer
game: Satisfactory
game: Soldat
game: Soldier of Fortune 2
game: Squad
game: Squad 44
game: Starbound
game: Stationeers
game: Sven Co-op
game: Team Fortress 2
game: Teamspeak 3
game: Teeworlds
game: Terraria
game: The Front
game: Unreal Tournament 2004
game: Unreal Tournament 3
game: Unreal Tournament 99
game: Unturned
game: Valheim
game: Wurm Unlimited
game: Zombie Master Reborn
game: label missing
good first issue
help wanted
info: alerts
info: dependency
info: docker
info: docs
info: email
info: query
info: steamcmd
info: systemd
info: tmux
info: website
info: website
needs more info
outcome: duplicate
outcome: issue resolved
outcome: issue resolved
outcome: issue unresolved
outcome: pr accepted
outcome: pr rejected
outcome: unconfirmed
outcome: wontfix
outcome: wrong forum
potential-duplicate
priority
pull-request
type: bug
type: feature
type: feature
type: feature request
type: game server request
type: refactor
waiting response
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/LinuxGSM#73
No description provided.