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.

  • Strit@lemmy.linuxuserspace.show
    3·
    7 months ago

    It has been default in Arch for a long time.

    What is the output of your df -h | grep tmpfs command? It should list a couple of devices using tmpfs, where /tmp is one of them.