News for hackers. Stuff that matters.
Re:Systemd, ten years later: a historical and technical retr... by mbreese on Sunday May 03, 2020 @11:21PM (#23064228)
I don’t know if these even exist anymore, but I’m imagining a class that meets in a room of workstations. Students can login to any workstation in the room. In this kind of shared environment, you may not want to have a student start a screen session and use the resources of a workstation when they logout. They could be sucking up cpu time from the next person to log in (from the next class).

It’s a scenario that might make sense here. But then again, having a watchdog script just kill leftover processes has been doing this same job for forever. Including this use case in systemd seems like overreach.

Re:Systemd, ten years later: a historical and technical retr... by dooglius on Sunday May 03, 2020 @11:55PM (#23064408)
Yeah, these still exist, though they're becoming more rare. I think what you actually want though is for processes to be killed at the end of class/lab period (even then, I think this should be done by students manually to avoid losing unsaved work). For example, say a student is running some big batch job as part of a lab. Now, if he wants to, say, go to the bathroom or go to the whiteboard to consult with other students, he has to either leave the computer unlocked (possibly leaving neighbors access to private student account data) or kill the running job.
Re:Systemd, ten years later: a historical and technical retr... by throw0101a on Monday May 04, 2020 @06:55AM (#23066532)
> It’s a scenario that might make sense here.

Perhaps. I have worked half my career in academia & research, going back to when Solaris (SPARC) workstations were a thing, and this was never a problem.