Also I woke up and my instance was down because something is playing Hide The Ball with all my RAM.

I mean even killing everything but base system processes doesn't free it. So it's probably systemd somehow.

That's going to be fun to figure out.

...or maybe it was the 1.1gb aborted go build in /tmp

ha ha... ha..... uuugggghhhh.

@trysdyn Huh! Why would an aborted build be taking up memory? Or does /tmp itself live entirely in memory or something?

@socks /tmp is, on most distros, a tmpfs, which is a ramdisk yeah.

Follow

@trysdyn @socks I never ran into that, it's not default in Debian or Ubuntu as far as I can tell

· · Web · 1 · 0 · 0

@noiob @socks Huh. Looks like the systemd unit is there but disabled by default and you can enable it by enabling tmp.mount.

It's just on by default on the entire RH family, Arch, Void...

@trysdyn @socks I guess if it's easy to enable keeping it off might stop people from accidentally filling up their RAM

@trysdyn my debians don't seem to ship with tmp.mount (it seems like that gets autogenerated from fstab?)

Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!