6 ms·
I think this is actually a useful change in default behavior for server environments, which comprise the vast majority of Linux installations. Being able to as
by otterley 10y ago
I think this is actually a useful change in default behavior for server environments, which comprise the vast majority of Linux installations.
Being able to assure by default that all of a user's spawned processes are terminated when the user logs out is a much more secure default behavior than the opposite. This means if I disable a user in LDAP and force the user to log out, I don't have to worry about lingering processes that might be malicious or pose some sort of threat to my server or data.
Keep in mind that there is a switch in logind to enable lingering that you can enable if you don't like it.
Besides, the release notes provided the workaround in line, so that interested users wouldn't have to hunt for a solution.
- Nursie 10y agoFor most development server use-cases, it's pretty terrible though. Screen is how a lot of people work.
- ams6110 10y agoYep -- I use tmux myself, but I'll have tmux sessions running for months on my work machine, so that I can ssh in and be immediately productive from anywhere.
- feld 10y agoIt's a POLA violation. Documenting this gross violation of expectations is not a sufficient apology.
- geofft 10y ago(I assume you meant POLS, not POLA?)
- wtallis 10y ago> Besides, the release notes provided the workaround in line, so that interested users wouldn't have to hunt for a solution. Only if the interested user is astute enough to put systemd at the top of the suspect list for why screen and tmux stopped working.
- otterley 10y agoIndividual users aren't the target audience, though. System integrators are. Your distribution maintainer is responsible for reading the change log and making the necessary decisions with respect to default configuration, notifying users, etc.
- stephenr 10y agoAssume anything wacky is a result of systemd. Problem solved. I'm only half joking.
- nisa 10y agoIs this really an unsolved problem? If you need that functionality can't you do it with ps or pkill -U and an alias? This approach also allows you to send SIGTERM first. http://unix.stackexchange.com/a/136552/34801 http://unix.stackexchange.com/a/136552/34801 it's 2 lines. It's also fine when systemd allows it as an easy knob and cgroups might catch something that pam doesn't (but you could also use cgroups in the pam script and cleanup/atd/cron or systemd timers). But doing it by default behavior is kind of surprising. > Besides, the release notes provided the workaround in line, so that interested users wouldn't have to hunt for a solution. The Hitchhiker's Guide to the Galaxy approach to announcements ;) But it was announced on the CHANGES file on that github repository works really well for breaking POSIX.
- wtbob 10y ago> Being able to assure by default that all of a user's spawned processes are terminated when the user logs out is a much more secure default behavior than the opposite. When the user has explicitly requested that processes not terminate when he hangs up by using the nohup command, that is precisely what not to do. This is fundamentally broken behaviour. > Besides, the release notes provided the workaround in line, so that interested users wouldn't have to hunt for a solution. In honour of Towel Day: Mr Prosser: But, Mr Dent, the plans have been available in the local planning office for the last nine months. Arthur: Oh yes, well as soon as I heard I went straight round to see them, yesterday afternoon. You hadn’t exactly gone out of your way to call attention to them had you? I mean like actually telling anybody or anything. Mr Prosser: But the plans were on display… Arthur: On display? I eventually had to go down to the cellar to find them. Mr Prosser: That’s the display department. Arthur: With a torch. Mr Prosser: The lights had probably gone out. Arthur: So had the stairs. Mr Prosser: But look, you found the notice, didn’t you? Arthur: Yes yes I did. It was on display at the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying beware of the leopard. End users cannot be expected to read the release notes for each release of something their distribution forces on them.
- otterley 10y agoAs I said elsewhere, the distribution maintainers are the target audience, not the individual users. This isn't yet a problem for the vast majority of users yet because the consequences have not made it to them. It's reasonable to expect appropriate arrangements will be made before then.