Read the other recent discussion on Debian moving to mount /tmp as tmpfs in upcoming stable release. It’s just confusing at the least if not a bad idea outright that systemd-tmpfiles goes out to delete files in /tmp regardless of how and by whom files were created. /tmp is a shared folder.
Guys, look. You know when I say systemd is evil and will screw you over, and never like any of my examples?<p>HERE. RIGHT HERE. This is the evil and/or incompetence <i>I don't want interacting with my machines</i>. I, and the rest of the community, frankly, is being held hostage.
After only reading the headline, I expected Poettering to be quoted saying, "Functioning as designed. Go pound sand." The response was as expected, but apparently Poettering's attitude has become contagious within the systemd devs:<p>> Initially the bug report was shot down by systemd developer Luca Boccassi of Microsoft with:<p>> So an option that is literally documented as saying "all files and directories created by a tmpfiles.d/ entry will be deleted", that you knew nothing about, sounded like a "good idea"? Did you even go and look what tmpfiles.d entries you had beforehand?<p>> Maybe don't just run random commands that you know nothing about, while ignoring what the documentation tells you? Just a thought eh