AlliedModders - Nemrun for SteamCMD Linux

AlliedModders (https://forums.alliedmods.net/index.php)

- Source Servers (SRCDS) (https://forums.alliedmods.net/forumdisplay.php?f=130)

- - Nemrun for SteamCMD Linux (https://forums.alliedmods.net/showthread.php?t=218555)

Re: Nemrun for SteamCMD Linux

Quote:

Originally Posted by ph (Post 2166902)

For windows ?

Nemrun is Linux only.

To be clear, I didn't write Nemrun (Nephyrin did that), I just updated it to work with SteamCMD.

Re: Nemrun for SteamCMD Linux

In the example there is some use of taskset. Can you explain how this works and if there is any use to it?

Re: Nemrun for SteamCMD Linux

Quote:

Originally Posted by moxie2020 (Post 2213813)

In the example there is some use of taskset. Can you explain how this works and if there is any use to it?

taskset is used to control which cores a server can use. It can be handy if you're running multiple servers from the same machine.

However, by the same token, TF2 and DOTA's replay systems can do things on other threads, so limiting those to a single CPU forces it to do that processing on the same CPU core.

Side note: CPU cores are 0-numbered, so a 4 core processor has cores 0-3. Of course, to specify core numbers, you use the -c argument to taskset... it's a lot easier than using bitmasks.

Re: Nemrun for SteamCMD Linux

Quote:

Originally Posted by Chdata (Post 2224795)

tbh I have no idea what nemrun is meant to do. It's able to only do update checks / validate when the server actually needs to? ;o

Except I looked at it at a time where I had a headache.

OK, here's my current test server configuration. Note that it could probably be optimized more by making the server use sv_shutdown to do a delayed restart instead of its normal shutdown command.

Spoiler

tf2_updater.sh:

Code:

#!/bin/bash

# Source Dedicated Server Init Script for Nemrun



# Server options

NAME='updater'                          # Server handle for the screen session

STEAM='/home/tf2/tf2'             # Path to STEAM installation

USER='tf2'



AFTERCMD=/home/tf2/tf2_copyso.sh



STEAM_DIR='../steamcmd'

STEAMCMD_SCRIPT='tf2update.txt'

SHARED_SCREENS='tf2'

cd $STEAM



screen -d -m -U -S $NAME ./nemrun-steamcmd \

-nemlog "runlogs/updater_%Y%m%d%H%M%S.log" \

-cleandownloads 10 -autoupdate -steam_dir $STEAM_DIR \

-steamcmd_script $STEAMCMD_SCRIPT -sharedscreens $SHARED_SCREENS -updatefirst \

-afternotifycmd $AFTERCMD \

-game tf -updatedaemon

-afternotifycmd is something I recently added to make a copy of server_srv.so for plugin development reasons. It occurs after the update completes.

I've considered adding a -sharedkillcommand "sv_shutdown_timeout_minutes 10; sv_shutdown; sm_csay \"Server will shut down in 10 minutes due to update\"" instead of doing an instant restart, but haven't tested it.

Now, the actual server, prophunt_server.sh:

Code:

#!/bin/bash

# Source Dedicated Server Init Script for Nemrun



# Server options

TITLE='Source Dedicated Server'         # Script initialization title

LONGNAME='Team Fortress 2'              # Full title of game type

NAME='tf2'                              # Server handle for the screen session

DAEMON='srcds_run'                      # The server daemon

STEAM='/home/tf2/tf2'            # Path to STEAM installation

USER='tf2'



# Game options

IP='1.2.3.4'                      # IP of the server

PORT='27015'                            # Port number to use

MAP='ph_lumberyard_a2'

MAPCYCLE='mapcycle-prophunt.txt'

GAME='tf'                               # Game type (tf|cstrike|valve|hl2mp)

SIZE='24'                               # Maximum number of players

CONFIGFILE='server-prophunt.cfg'        # Config file to use in cfg directory

REPLAYDIR='blu'                         # Replay subdirectory for this server

CORES='1-3'                             # CPU cores to use

SOURCEMOD='addons/sourcemod-prophunt'

MOTDFILE='motd-prophunt'

AUTOEXEC='autoexec_normal.cfg'

cd $STEAM



# Server options string

# OPTS="-game $GAME +hostname \"$TITLE\" +randommap -ip $IP -port $PORT \

OPTS="-game $GAME +hostname \"$TITLE\" +map ${MAP} -ip ${IP} -port ${PORT} \

    +maxplayers ${SIZE} +sv_pure 1 +mapcyclefile ${MAPCYCLE} \

    +servercfgfile ${CONFIGFILE} -strictportbind +sm_basepath $SOURCEMOD \

    +motdfile ${MOTDFILE}.txt +motdfile_text ${MOTDFILE}_text.txt \

    +exec ${AUTOEXEC}"

#    -replay"



# screen -d -m -U -S $NAME $STEAM/$DAEMON $OPTS



screen -d -m -U -S $NAME ./nemrun-steamcmd \

-nemlog "runlogs/tf2_%Y%m%d%H%M%S.log" \

-corefile "cores/tf2_%Y%m%d%H%M%S.core" \

\

$OPTS

The important part of this script is the part at the end, but I included the entire thing just to make sure I didn't forget anything. The NAME should match the SHARED_SCREENS from the first script. Note that SHARED_SCREENS is a comma-separated list of all TF2 servers you want to restart.

Re: Nemrun for SteamCMD Linux

Can I have an example of a 'unified' steamCMD script?

Because currently I use something like...

vsh_dis.txt

Code:

@ShutdownOnFailedCommand 1

@NoPromptForPassword 1

login anonymous

force_install_dir ../vsh

app_update 232250 validate

exit

And there's another one for each of my other two servers that only changes the folder.

Also I'm just going to assume one first executes 'tf2_updater.sh' and then 'prophunt_server.sh' or 'whatever.sh' for all of one's servers?

And from there this thing handles autoupdating them... or not going through a full file check if there's no need to?

Also... I don't see anything that shuts down the server in what you posted? No kill or quit or exit or restart or shutdown command seems to be in the snippet you posted.

Chdata awaits the day his question is answered clearly.

Re: Nemrun for SteamCMD Linux

Quote:

Originally Posted by Chdata (Post 2251306)

Can I have an example of a 'unified' steamCMD script?

Because currently I use something like...

vsh_dis.txt

Code:

@ShutdownOnFailedCommand 1

@NoPromptForPassword 1

login anonymous

force_install_dir ../vsh

app_update 232250 validate

exit

nemrun is intended to be used with screen. The -sharedscreens argument is a comma-separated list of named screens (-S in the screen command-line) that it should send a "quit" command to. Since these screens were presumably also started with nemrun, they will auto-restart when they get the quit command.

Do note that it's possible to run a custom shell script instead using the -shutdownscript command-line argument or change which command is sent to servers using -sharedkillcommand .

Re: Nemrun for SteamCMD Linux