It is not "abuse of /tmp" to put files there, even if they need to be there for a long time. That is an unnecessary characterization.
Yes, /tmp gets backed up along with the rest of the system on every VM in my environment.
Sometimes "temporary" CAN mean "weeks or even months." That's not something that needs to be determined in advance by someone else.
This is keeping in mind that I, myself, said that I would be fine with /tmp as a tmpfs. I wouldn't cry at all if /tmp were cleaned out at boot time (which could be weeks or even months).
But a) at boot time, all processes have been restarted. It would be an exceptional process that needs to resume after a reboot using data in /tmp (though not impossible) and...
...perhaps more importantly, b) I wouldn't want to declare on behalf of all Debian users that doing so Is Wrong And You Should Not Do It. That strikes me as unnecessarily presumptuous.
It's one thing to support a change that MY systems can cope with. It's quite another to declare that EVERYONE will now use these rules, particularly when it means deleting their files.
Even after a reboot, I would be upset to lose the debug files that I've been accumulating for several days while trying to track down an intermittent problem with this stupid VPN...
Sent from my mobile device.
Then it will be high time you learn not to abuse /tmp that way
I'm a bit surprised how many people seem to really rely on data in /tmp
to survive for weeks or even months. I wonder if they backup /tmp?
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
"When one man dies it's a tragedy. When thousands die it's statistics."
(Stalin commenting the worlds reaction on Covid 19.)