LinuxGSM Config

Search…
LinuxGSM Config
LinuxGSM Configs and Game Server Configs are different. One is the config for LinuxGSM itself and the other is for the game server instance.
LinuxGSM configuration is managed using multiple config files loaded in a set order. It is important to understand how these config files work to make sure settings are placed in the correct config files.
Config Files Location
Relative to your installation directory, config files are located in:
1
lgsm/config-lgsm/gameserver
Copied!
Configuration Mechanism
The LinuxGSM config mechanism is designed to allow the users to benefit from new features, maintain default settings, better manage multiple instances and allow LinuxGSM to update the config if required.
Configuration files
An understanding of how LinuxGSM handles multiple game server instances helps.
_default.cfg
_default.cfg is the template config, this file is a base of all available default settings. It can not be edited and is updated by LinuxGSM when using ./gameserver update-lgsm. This config is loaded first.
Do not edit _default.cfg any changes to this file will be overwritten.
common.cfg
common.cfg is used for common settings that apply to all game server instances of the same installation. This saves having to apply the same settings multiple times.
instance.cfg
instance.cfg is the configuration file used for each individual game server instance. Settings here will only apply to this specific game server instance. This config file takes the same name as the game server instance name ./gameserver. For example, if ./csgoserver is used the instance.cfg will be called csgoserver.cfg. This config is last to be loaded.
Secret Configs
Secret configs are not encrypted, but a place to store sensitive info away from other configs.
The secret configs are a place to put sensitive information such as steam login details away from the main config files. This is done to allow server admins to backup their configs while excluding sensitive information. This is particularly useful for admins who want to create a version-controlled skeleton configuration using git that they might want to make public.
It is important to know that the secret config is NOT encrypted or any more secure than other configs.
A secret config can be identified with the word secrets prepended to the front of the config name.
Config Load Priority
When LinuxGSM is loading the configs they will load in order. First taking settings from _default.cfg then common.cfg and finally instance.cfg. This means that any setting set in instance.cfg will override that setting in common.cfg which in turn will override the setting in _default.cfg.
LinuxGSM config load order
1
_default.cfg -> common.cfg -> instance.cfg
Copied!
How to Use
Simple Configuration
This configuration fits most scenarios, where you have a simple installation with only one instance.
1.Browse to the config-lgsm directory
1
cd lgsm/config-lgsm/
Copied!
1.Use ls to list the directory contents and find the name of your instance.cfg.
2.Use cat or nano to see the contents of _default.cfg .
1
cat _default.cfg
Copied!
1.Copy the individual settings you want to change to instance.cfg
It is recommended you only copy settings you want to change from _default.cfg into instance.cfg. If any settings in _default.cfg are updated with a new release of LinuxGSM they may not be picked up if all the settings have been copied.
Multiple Instances Configuration
This configuration is useful for multiple instances.
1.Browse to the config-lgsm directory
1
cd lgsm/config-lgsm/
Copied!
1.Use ls to list the directory contents.
2.Use cat or nano to see the contents of _default.cfg .
3.Copy any settings you want to apply to all instances to common.cfg.
It is recommended you only copy settings you want to change from _default.cfg into instance.cfg. If any settings in _default.cfg are updated with a new release of LinuxGSM they may not be picked up if all the settings have been copied.
1.Copy any settings you want to apply to a specific instance to its instance.cfg.
1
csgoserver.cfg
2
csgoserver-2.cfg
Copied!
Examples
Example 1
Load de_nuke as default map on csgoserver:
1
_default.cfg: defaultmap="de_dust2"
2
common.cfg: NOT SET
3
csgoserver.cfg: defaultmap="de_nuke"
Copied!
Example 2
Load cs_office as default map on csgoserver:
1
_default.cfg: defaultmap="de_dust2"
2
common.cfg: defaultmap="cs_office"
3
csgoserver.cfg: NOT SET
Copied!
Example 3
Load de_dust2 as default map on csgoserver:
1
_default.cfg: defaultmap="de_dust2"
2
common.cfg: NOT SET
3
csgoserver.cfg: NOT SET
Copied!
Example 4
Load de_nuke as default map on csgoserver instance and de_inferno on csgoserver-2 instance:
1
_default.cfg: defaultmap="de_dust2"
2
common.cfg: defaultmap="de_inferno"
3
csgoserver.cfg: defaultmap="de_nuke"
4
csgoserver-2.cfg: NOT SET
Copied!
Example 5
Load de_nuke as default map on csgoserver instance and cs_office on csgoserver-2 instance:
1
_default.cfg: defaultmap="de_dust2"
2
common.cfg: NOT SET
3
csgoserver.cfg: defaultmap="de_nuke"
4
csgoserver-2.cfg: defaultmap="cs_office"
Copied!
Configuration
Game Server Config
Last modified 1yr ago
Export as PDF
Copy link
Contents
Config Files Location
Configuration Mechanism
Multiple Instances Configuration
Examples