Skip to main content

What still runs after you disconnect a Rust manager?

Identify where jobs run before you disconnect the old manager. Stopping a dashboard connection may leave a job running on the host. Conversely, a job that only lived in the dashboard may stop sending its player notices as soon as the connection goes away.

Make a list of jobs and where they run

Read the old dashboard schedules, the host’s own scheduler and any rental panel schedules. Check jobs that start or stop Rust, send messages or check whether it has crashed. LinuxGSM, for example, documents its monitor as an automatable command, and systemd timers can activate their own services independently. Each job on your list needs an owner after the change or a decision to retire it.

Ask the old tool’s publisher what disconnecting or uninstalling does to jobs it installed on the host. Use its documented removal path. Check a spare host first if you need to know what it will leave behind.

Watch for both missing and duplicate work

After you switch, check the next planned run for a moved job. It should appear in the new place with the expected result. For a retired job, check that the old place shows it disabled and that its next former run does not send anything. Keep the owner and next check beside each open item until you can account for it.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details