GSP/GSP-Agent-Windows
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fixed server_stopped file check

Browse source
This commit is contained in:
Frank Harris 2026-06-10 18:37:40 -04:00
parent a1f1f8529f
commit 1d04e2a4e8
2 changed files with 32 additions and 48 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/PROCESS_MANAGEMENT.md
View file

@ -48,12 +48,15 @@ Tracked fields include PID/session information used to stop the right process re
When stop is requested, the agent now:
1. marks status hint as `STOPPING`
2. creates `SERVER_STOPPED` marker for autorestart handling
3. removes startup flag for `<ip>-<port>`
4. kills tracked PIDs (`screen_pid`, `windows_pid`, `game_pid`) if present
5. kills managed screen session
6. checks if the game port is still listening and kills the owning PID
7. verifies stop success (no managed session, no tracked running PID, no listening game port)
2. removes startup flag for `<ip>-<port>`
3. kills tracked PIDs (`screen_pid`, `windows_pid`, `game_pid`) if present
4. kills managed screen session
5. checks if the game port is still listening and kills the owning PID
6. verifies stop success (no managed session, no tracked running PID, no listening game port)
7. writes status hint `STOPPED` only after verification passes
The agent no longer creates or reads `SERVER_STOPPED`/`Server_Stopped` marker files for lifecycle control.
Autorestart loop control now uses agent-owned runtime status hints (`STARTING`/`STOPPING`/`STOPPED`) instead of game-home marker files.
## Restart behavior