On Mon, 2 Mar, 2020 at 15:01, Tim via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Now, for some reason best known to themselves, the developers have
decided that instead of putting an entry in the fstab file (either for
a real partition or to use tmpfs in RAM), there's a systemd service
that sets up a tmpfs RAM-based tmp partition. The only reason I can
guess to do it that way, would be dynamic creation of more than one
tmpfs, on demand. Though I don't know if they do that.
There's multiple potential benefits. One is that some services on
startup assume an empty /tmp, another is that it helps for some
containers and chroots, and another is that it helps for live disks.
I don't know which benefit became the actual motivator. And yes, there
are drawbacks too.
If you want tmp to be on disc (e.g. because you create very large tmp
files while mastering DVDs and have limited RAM, or you need some tmp
files to survive a reboot), you need to stop and disable that service,
and go back to setting /tmp up the old way.
/tmp was never a good place to keep long-term files.
Some OS-es rm -rf /tmp at early boot, some OS-es that support slices
reformat /tmp on reboot. And Fedora used to switch on tmpwatch by
default which meant that /tmp was emptied weekly.
In Fedora, if you want disk-backed /tmp use /var/tmp and configure
tmpwatch. Services should honour TMPDIR=/var/tmp/
(apologies for the earlier empty mail)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
