Skip to content

Fix inverted SIGTSTP condition in IPC server#1915

Merged
gnodet merged 1 commit into
apache:masterfrom
gnodet:fix/ipc-server-sigtstp
Jun 9, 2026
Merged

Fix inverted SIGTSTP condition in IPC server#1915
gnodet merged 1 commit into
apache:masterfrom
gnodet:fix/ipc-server-sigtstp

Conversation

@gnodet

@gnodet gnodet commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

The condition for ignoring SIGTSTP in IpcServer.main() was inverted:

  • if (IpcClient.IS_WINDOWS) tried to register a SIGTSTP handler on Windows, where the signal does not exist — causing a crash at daemon startup.
  • On Unix (where SIGTSTP actually exists and is sent on Ctrl-Z), nothing was ignored — causing the IPC daemon to suspend alongside the client when the user pressed Ctrl-Z.

Fix: Negate the condition to if (!IpcClient.IS_WINDOWS) so that SIGTSTP is ignored on Unix only.

This is a one-character fix (! added) with no behavioral change on any OS other than making things work correctly:

  • Unix: SIGTSTP now properly ignored → daemon stays alive on Ctrl-Z ✓
  • Windows: SIGTSTP registration skipped → no crash ✓

The condition for ignoring SIGTSTP was inverted: it tried to
ignore TSTP on Windows (where it does not exist, causing a crash)
and did nothing on Unix (where TSTP exists, causing the daemon
to suspend on Ctrl-Z).

Fix: ignore SIGTSTP only on non-Windows (Unix) systems.
@gnodet gnodet merged commit b06e62f into apache:master Jun 9, 2026
14 checks passed
@gnodet gnodet changed the title [MNG-XXXX] Fix inverted SIGTSTP condition in IPC server Fix inverted SIGTSTP condition in IPC server Jun 9, 2026
@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

@gnodet Please assign appropriate label to PR according to the type of change.

@github-actions github-actions Bot added this to the 2.0.19 milestone Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants