Xpra: Ticket #1671: forward signals

Follow up from #1350: we now create a fake process for each server pid and we will receive signals sent by pagers and window managers, we should forward those to the real server-side process and let it decide what to do with it.

This will require:

Fri, 24 Nov 2017 16:41:44 GMT - Antoine Martin:

See also #1702

Wed, 13 Dec 2017 08:27:50 GMT - Antoine Martin: status, description changed

Support for SIGINT and SIGTERM forwarding added in r17608, with one important limitation: the watcher process exits when it receives any signal, so this can only be used once per watcher process.

Still TODO: keep watcher running after handling signals and communicate with parent process using stdin / stdout, listen for more signals (SIGUSR1, etc)

Wed, 13 Dec 2017 09:53:13 GMT - Antoine Martin: owner, status changed

Done in r17609 + r17616. The signals we now forward are: SIGINT, SIGTERM, SIGQUIT, SIGCONT, SIGUSR1, SIGUSR2. (this can be changed using the XPRA_WINDOW_SIGNALS env var)

@maxmylyn: mostly a FYI, you can send a signal to the pid of an xpra window and it will be forwarded to the server process.

Wed, 13 Dec 2017 17:19:31 GMT - J. Max Mena: status changed; resolution set

Neat. Noted. Closing.

Sun, 04 Nov 2018 13:38:55 GMT - Antoine Martin:

Caused a regression and now disabled for python2: #2025.

Sat, 23 Jan 2021 05:30:40 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1671