forward signals

[totaam]

Issue migrated from trac ticket # 1671

component: client | priority: major | resolution: fixed

2017-10-25 10:59:47: antoine created the issue

---

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:

• a new capability: "window.signals"
• a new server message: ["window-signal", wid, signal] (we send the wid and let the server find the real pid)

[totaam]

2017-11-24 16:41:44: antoine commented

---

See also #1702

[totaam]

2017-12-13 08:27:50: antoine changed status from new to assigned

[totaam]

2017-12-13 08:27:50: antoine edited the issue description

[totaam]

2017-12-13 08:27:50: antoine commented

---

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)

[totaam]

2017-12-13 09:53:14: antoine changed status from assigned to new

[totaam]

2017-12-13 09:53:14: antoine changed owner from antoine to maxmylyn

[totaam]

2017-12-13 09:53:14: antoine commented

---

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.

[totaam]

2017-12-13 17:19:32: maxmylyn changed status from new to closed

[totaam]

2017-12-13 17:19:32: maxmylyn set resolution to fixed

[totaam]

2017-12-13 17:19:32: maxmylyn commented

---

Neat. Noted. Closing.

[totaam]

2018-11-04 13:38:56: antoine commented

---

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