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?
misyl /
npub17k…472cl
2024-07-03 13:13:54
Author Public Key
npub17kucze4xm3p6ahuw7fuqrhv3j8mqfpdsh3aeyhvte7msf0hd520sc472clPublished at
2024-07-03 13:13:54Event JSON
{
"id": "ee3f3ecda687864b623a1413640591ce930a95a98487ab882bbcacb58725f04f",
"pubkey": "f5b98166a6dc43aedf8ef27801dd9191f60485b0bc7b925d8bcfb704beeda29f",
"created_at": 1720012434,
"kind": 1,
"tags": [
[
"proxy",
"https://idtech.space/objects/a71c83e8-5d69-4387-ac56-7d1f046db603",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://idtech.space/objects/a71c83e8-5d69-4387-ac56-7d1f046db603",
"pink.momostr"
],
[
"expiration",
"1722604779"
]
],
"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": "c2dc6a2665540d659fe115b484cef5be3426403358e2efeaf728d9d5bfc9cdc50304c6b2ab0869081578151abf752feeff885a5bd7adacd933f25cfbcca38068"
}