> And I'm kind of worried that when this breaks stuff, the systemd project is going to push forward with some plan to get rid of sudo, and not gracefully accept

> And I'm kind of worried that when this breaks stuff, the systemd project is going to push forward with some plan to get rid of sudo, and not gracefully accept the feedback that this is breaking things. See for example perhaps, "systemd can't handle the process previlege that belongs to user name starts with number, such as 0day": * https://github.com/systemd/systemd/issues/6237 https://github.com/systemd/systemd/issues/6237 Never mind that POSIX allows it: * https://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap03.html#tag_03_426 https://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd... * https://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap03.html#tag_03_276 https://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd... > I'm particularly worried about this because of the whole saga of KillUsersProcesses breaking nohup and screen, which to my knowledge is still broken many years later. For anyone curious, see "Systemd v230 kills background processes after user logs out, breaks screen, tmux" from 2016: * https://news.ycombinator.com/item?id=11782364 https://news.ycombinator.com/item?id=11782364