My /
is a tmpfs.
There is no state accumulating that I didn’t explicitly specify, exactly because I don’t want to deal with those kind of chores.
My /
is a tmpfs.
There is no state accumulating that I didn’t explicitly specify, exactly because I don’t want to deal with those kind of chores.
I don’t think they meant forcing themselves because their RAM would fill up, but because their stuff would be gone after rebooting if they didn’t move it.
DDG and Mullvad are private search engines as they strip out your trackable metadata and don’t pass on your IP address.
Is that so? How do you know?
I’m not using it at all, I use the *DAV functionality of my paid mail provider.
I did research on what solution I would use alternatively – with requirements very similar to the ones you proposed – and EteSync checked all the boxes, which is why I recommended it.
I set up an instance once, and it seemed to work just fine, but I haven’t thoroughly evaluated it.
Doesn’t that apply to any search engine?
I’ve been using SearXNG and its predecessor for years and I have no reason to change that. Highly recommend you check it out.
They don’t support DNSSEC.
How about EteSync?
I meant like in general…
I do agree it’s worth investigating if it happens again. My best guess so far would be some kind of data written to a tmpfs. That’d explain it not being associated with a particular process, yet counting towards actual used RAM.
Why do you care so much about memory usage?
Unused RAM is wasted RAM.
selber hs °^°