None of this is about trying to prevent the user from using resources. The user is the one who is logging out in the first place. If the user wants to terminate

None of this is about trying to prevent the user from using resources. The user is the one who is logging out in the first place. If the user wants to terminate all of their processes except for one daemon they can do that. The security benefits aren't the primary benefit, security wise all you gain is that after you log out there's no chance that anything with any sensitive information is still hanging around. I mentioned ssh-agent as an example but you could also have stuff like maybe chrome didn't close on SIGHUP and as a result maybe this makes your saved passwords accessible to someone who can dump the RAM later by getting physical access to it. It definitely helps security but it's not really that big of a deal. Ironically enough when I went to Google to search for an example the result that came up was my comments on HN on the same subject from a year and a half ago. https://news.ycombinator.com/item?id=14735145 https://news.ycombinator.com/item?id=14735145 Here's a great example of the kind of real life breakage that reaping the user scope on logout actually fixes. https://bugs.freedesktop.org/show_bug.cgi?id=94508 https://bugs.freedesktop.org/show_bug.cgi?id=94508