I get the idea behind it for sure but why use our available ram for this? I thought whatever init functionality would just wipe clean /tmp at boot.
Right now what I’m looking at is that if a system has 16gbram KDE Neon uses half of it for /tmp.
The thing is applications could output to /tmp for a plethora of reasons that could maximize that. Whether you are a content creator or processing data of some sort leaving trails in /tmp the least I want is my ram being used for this thing regardless.
Basically if you drop-in a 10GB file in /tmp right now (if your setup has tmpfs active) you will see a 10GB usage in your htop. Example in https://imgur.com/a/S9JIz9p
I’m not here to pick a fight but as a new KDE Neon user I’m scratching my head on the why after years in Arch Linux.
Arch uses tmpfs for /tmp by default as well. At least on my.install from 2-3 years ago
I… don’t think I have ever seen it do that automatically unless I missed some steps in the installation guide…? most of the time I just created the partitions I needed. I did a quick CTRL + F on tmpfs or tmp but not seeing anything…
Anyhow, I don’t see on my desktop which still has Arch Linux installed which I want to move to KDE Neon but extremely lazy when you have an immense backup to do…
It’s default since systemd afaik. I think
systemd-tmpfilesmanages this. It’s never been a problem for me, it pretty much remains fairly empty most of the time. Most things like sockets are in/runwhich is also tmpfs.It has been default in Arch for a long time.
What is the output of your
df -h | grep tmpfscommand? It should list a couple of devices using tmpfs, where /tmp is one of them.