xpra icon
Bug tracker and wiki

Opened 6 months ago

Closed 4 months ago

#1671 closed enhancement (fixed)

forward signals

Reported by: Antoine Martin Owned by: J. Max Mena
Priority: major Milestone: 2.3
Component: client Version: trunk
Keywords: Cc:

Description (last modified by Antoine Martin)

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)

Change History (4)

comment:1 Changed 5 months ago by Antoine Martin

See also #1702

comment:2 Changed 4 months ago by Antoine Martin

Description: modified (diff)
Status: newassigned

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)

Last edited 4 months ago by Antoine Martin (previous) (diff)

comment:3 Changed 4 months ago by Antoine Martin

Owner: changed from Antoine Martin to J. Max Mena
Status: assignednew

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.

Last edited 4 months ago by Antoine Martin (previous) (diff)

comment:4 Changed 4 months ago by J. Max Mena

Resolution: fixed
Status: newclosed

Neat. Noted. Closing.

Note: See TracTickets for help on using tickets.