Systemd 256.1: Now slightly less likely to delete /home | Hacker News Reader

Systemd 256.1: Now slightly less likely to delete /home

theregister.com

27 pointsraybb7 comments

They really should have renamed it systemd-files five years ago, it might have let the user know it wasn’t just purging tmp

https://github.com/systemd/systemd/issues/12447

if anything systemd-sysfiles, but this is exactly what they meant with bikeshedding.

Lol: "Fixes -catastrophic data loss-, er, -bug-, er -poorly documented feature-... user error"

[Author here]

I try. :-D

i have issue with it automatically deleting files from /tmp which is a shared dir:

  $ cat /usr/lib/tmpfiles.d/tmp.conf
  q /tmp 1777 root root 10d
  q /var/tmp 1777 root root 30d

How likely is someone gonna look at those files if they haven't been even accessed in the last 10/30 days?

It checks ctime, mtime and atime to determine if it should remove the file (or you can also flock(2) them) and if any of them are less than the time it doesn't.

> Systemd 256.1: Now slightly less likely to delete /home

That's why ransomware runs on Windows. On linux, with SystemD [1], there is nothing to ransom. /s

[1] I run Slackware.

Reply on news.ycombinator.com