Matus, I don't totally need to make /var a tmpfs, it's just out of curiosity, and for the simplicity of configuration. Since /var/cache and /var/log are already tmpfs for me, and this extendet tmpfs setup works fine since at least 2 years, it seems to be interesting to check the other top folders of /var for that option too.
> On 22.10.18 10:02, Michael wrote: > >Recently made a lot of stuff tmpfs (like /tmp and /var/cache and > >$HOME/.cache) and i'm not sure about this ...: > > > >Is there any reason why /var cannot be completely tmpfs ? > > /var contains huge amount of data that keep changing but must not be lost. ok, but shouldn't /var contain no configuration-like files ? In other words, are these all files to read or are they just only re-created everytime, thus only to write ? If so, then perhaps could i live with some extra time for starting services / apps to re-create things (if it's only within a second). For example, here are my /var topfolders: apt -> empty backups -> write-only; and i did never need these in about 15 years, so i guess i can live without. cache -> already tmpfs lib -> don't know XXX local -> empty lock -> only a lockfile log -> already tmpfs for me (if i ever need persistent logs, for specific reason, i'll just revert it. It's a desktop machine, rarely problems.) mail -> don't need opt -> empty run -> already tmpf via Debian spool -> cron/anacron, cups .... i guess, no need for persistent tmp -> empty www -> not used here That leaves /var/lib as a main candidate for problems, because i don't know the usage of what is stored here. ps. About /var/cache/apt, it is mounted as separate 5G partition. /tmp already is made tmpfs.
