From 4185d621f8ab302976d029d7f60383a5979e6079 Mon Sep 17 00:00:00 2001
From: fourbites <yppdev25@gmail.com>
Date: Sat, 13 Dec 2025 12:04:16 +0100
Subject: [PATCH] Prevent overlapping reboot warning messages

It's hard to say if this is the cause, but it won't hurt to clear existing intervals just in case.
---
 .../java/com/threerings/presents/server/RebootManager.java  | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/core/src/main/java/com/threerings/presents/server/RebootManager.java b/core/src/main/java/com/threerings/presents/server/RebootManager.java
index 2936c0037..548b04ddd 100644
--- a/core/src/main/java/com/threerings/presents/server/RebootManager.java
+++ b/core/src/main/java/com/threerings/presents/server/RebootManager.java
@@ -282,6 +282,9 @@ public abstract class RebootManager
         // schedule the next warning
         final int nextLevel = level + 1;
         final int nextMinutes = (nextLevel == warnings.length) ? 0 : warnings[nextLevel];
+        if (_interval != null) {
+            _interval.cancel();
+        }
         _interval = _omgr.newInterval(new Runnable() {
             public void run () {
                 doWarning(nextLevel, nextMinutes);
@@ -303,6 +306,9 @@ public abstract class RebootManager
 
         log.info("Reboot delayed due to outstanding locks", "locks", _rebootLocks.elements());
         broadcast("m.reboot_delayed");
+        if (_interval != null) {
+            _interval.cancel();
+        }
         (_interval = _omgr.newInterval(new Runnable() {
             public void run () {
                 doWarning(getWarnings().length, 0);