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.

  • mox@lemmy.sdf.org
    71·
    7 months ago

    Why would it matter the reason of dropping a file of X size? The point is that not all applications are “decent” and some will undoubtedly use /tmp because “it might be the most logical thing” for any developer that’s not really up to date.

    It matters because it’s the difference between a real-world situation, and a fabricated scenario that you expect to be problematic but doesn’t generally happen.

    All filesystems have limits, and /tmp in particular has traditionally been sized much smaller than the root or home filesystems, regardless of what backing store is used. This has been true for as long as unix has existed, because making it large by default was (and is) usually a waste of disk space. Making it a tmpfs doesn’t change much.

    The point is that not all applications are “decent” and some will undoubtedly use /tmp because “it might be the most logical thing” for any developer that’s not really up to date.

    In my experience, the developers of such applications discover their mistake pretty quickly after their apps start seeing wide use, when their users complain about /tmp filling up and causing failures. The devs then fix their code. That’s why we don’t see it often in practice.

    I don’t see how reviewing the tmpfs helps in this scenario if at all…

    I mentioned it in case it helps you to understand that the memory is used more efficiently than you might think. Perhaps that could relieve some of your concern about using it on a 16GB system. Perhaps not. Just trying to help.

    we are talking about end-users your common joe/dane running your day to day applications, whatever they may be.

    We are? I don’t see them echoing your concerns. Perhaps that’s because this is seldom a problem.

    • lumirell@lemmy.kde.socialOP
      21·
      7 months ago

      In my experience, the developers of such applications discover their mistake pretty quickly after their apps start seeing wide use, when their users complain about /tmp filling up and causing failures. The devs then fix their code. That’s why we don’t see it often in practice.

      I humbly disagree. We don’t live in that utopia.

      I don’t see them echoing your concerns.

      I guess for an scenario to be real everyone has to know exactly what’s happening? They will know what caused it and they will all know how to properly report it even though I don’t even expect a lot of people to know their system especially your average joe/dane nor do I expect them to even troubleshoot the issue if something were to happen. It doesn’t really invalidate the scenario at all.

      A fabricated scenario is itself pretty redundant. :)