News for hackers. Stuff that matters.
Re:Systemd as tragedy by majewsky on Tuesday January 29, 2019 @05:06AM (#19025157)
Like it or not, the Linux kernel is clearly the outlier in terms of backwards compatibility. For example, Postgres changes their data format in most non-bugfix releases. Would you consider that "a strike against" Postgres?
Re:Systemd as tragedy by dooglius on Tuesday January 29, 2019 @06:34AM (#19025517)
They provide an upgrade process that makes this invisible to the end user, so it's not a fair comparison. If it started deleting tables when I exit a session, that would definitely be a strike against it.
Re:Systemd as tragedy by SahAssar on Tuesday January 29, 2019 @05:43PM (#19030582)
Postgres has session-bound resources, and in most cases no way to disable those from being deleted when exiting a session. For example in postgres you can't persist a prepared statement, but you can of course persist data within a table. Any function running will be killed when you exit (or at least not complete since the transaction is cancelled).

IMO when a user has logged out and has not had the permissions/foresight to setup a task in the system to run without a session it should be killed.

I get that this has not been the default behavior in linux/UNIX, but to me it seems like the sensible one.

And that's before we ever argue about the possibility to turn it off.

Re:Systemd as tragedy by m45t3r on Tuesday January 29, 2019 @01:41PM (#19028803)
Systemd offer a compile and runtime option to turn this option off, so it is a fair comparison.