[Feature]: Additional options for monitor to be able to run a script when it restarts server
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start with the monitor command entry point and the rustserver.cfg handling described in the issue. Trace where a stopped server is detected and restarted, then define the configuration path for a pre-restart script. Done means the configured script runs before monitor restarts the server and the existing restart behavior remains intact.
Written by the indexing model from the issue text.
Description
User story
As server admin I want to improve automation for monitoring
Game
Rust but this feature may assist other games too
Linux distro
Other
Command
command: monitor
Further information
Rust fas a plugin named SmoothRestarter that can stop the server to allow the controlling script to perform an update for rust or oxide. It alerts the players to let them get back to base etc. If I allow it to stop the server when an oxide update is available, it stops the server, then monitor restarts it, but as I cant have it run another script, oxide is not updated. This cycle continues forever. Currently I have had to disable this feature as LinuxGSM doesnt appear to have an option to execute a script when monitor detects a stopped server.
It would be very useful if an option was added to rustserver.cfg to be able to specify a script to be run just prior to the restart to allow any updates to be performed.
- Dominant language
- Shell
- Stars
- 4.9k
- Forks
- 866
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 100
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GameServerManagers/LinuxGSM
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
GameServerManagers/LinuxGSM#5241 ·
Maintainers usually reply within 1 day
-
command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
GameServerManagers/LinuxGSM#5240 ·
Maintainers usually reply within 1 day
-
command: monitor distro: Ubuntu engine: spark game: Natural Selection 2 info: query reproducible: unable severity: critical type: bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
GameServerManagers/LinuxGSM#5238 ·
Maintainers usually reply within 1 day
-
engine: null game: Teamspeak 3
Difficulty 3/5 Half a day Newbie friendliness 66/100
GameServerManagers/LinuxGSM#5237 ·
Maintainers usually reply within 1 day
All issues in GameServerManagers/LinuxGSM
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100