[Feature]: Additional options for monitor to be able to run a script when it restarts server

Open
#4,554 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
linux, shell
Domain
cli, devops

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

command: monitor game: Rust info: alerts type: feature
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

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GameServerManagers/LinuxGSM

All issues in GameServerManagers/LinuxGSM

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.