I am having a horrible time trying to make Gamescope's shutdown more robust.
It essentially needs to act as a subreaper that also kills all of it's children on death -- even if Gamescope crashes.
Why is that so damn hard and annoying to implement? I feel like I am missing something obvious.
I've tried signal handler stuff, a child watchdog process that kills all of it's children, but nothing seems perfectly robust.
What am I missing?
Joshua Ashton /
npub1nh…knufj
2024-07-03 15:13:54
Author Public Key
npub1nhjtk9tspwhtgrv785ylrv9l963skcjmywlgj40pp34hhxghe3ts3knufjPublished at
2024-07-03 15:13:54Event JSON
{
"id": "592dc86738b21cdc44866fe05025ffc4920ea245a1a01b3459ebc3160834926b",
"pubkey": "9de4bb15700baeb40d9e3d09f1b0bf2ea30b625b23be8955e10c6b7b9917cc57",
"created_at": 1720012434,
"kind": 1,
"tags": [
[
"proxy",
"https://idtech.space/objects/a71c83e8-5d69-4387-ac56-7d1f046db603",
"activitypub"
]
],
"content": "I am having a horrible time trying to make Gamescope's shutdown more robust.\n\nIt essentially needs to act as a subreaper that also kills all of it's children on death -- even if Gamescope crashes.\n\nWhy is that so damn hard and annoying to implement? I feel like I am missing something obvious.\n\nI've tried signal handler stuff, a child watchdog process that kills all of it's children, but nothing seems perfectly robust.\n\nWhat am I missing?",
"sig": "2d85ef8d9abd2fecf545cbc0f9d22a51dbe7a84fdf471b4f3f13db52faeecef65bd3bbc600574b828c3e3dc5a084a68a535c4e1bc55afa5c13cb8bfd80d1c7ca"
}