Skip to content

A few suggestions for l4d2server script #96

Closed

Description

@patriotgames

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

Activity

  1. dgibbs64 commented on Jun 21, 2014

    @dgibbs64
    Member

    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.

  2. dgibbs64 commented on Jun 21, 2014

    @dgibbs64
    Member

    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 :)

  3. self-assigned this
    on Jun 21, 2014
  4. twinsuns commented on Aug 3, 2014

    @twinsuns

    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.

  5. lock commented on Jul 20, 2018

    @lock

    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.

  6. locked as resolved and limited conversation to collaborators on Jul 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions