Daniel Xu

In ``` 1377(ssh-agent)[E1] 1401(tmux: server)[E1] 1402(zsh)[E1] ``` `E1` means kill(, SIGKILL) failed with EPERM. Is oomd running with the right permissions? In ``` Unable to set xattr trusted.oomd_kill=0 on /sys/fs/cgroup/user.slice/user-1000.slice/[email protected]/gnome-terminal-server.service....

This is the kill code: https://github.com/facebookincubator/oomd/blob/master/src/oomd/plugins/BaseKillPlugin.cpp#L138 > cryptic trusted.oomd_kill = 0 attributes. What is this attribute, is it related to a facebook contributed kernel module? It's an extended attribute. See...

Can you also share the oomd config you're using?

Yeah I've been talking with Johannes about this. It'll be nice for oomd to have edge triggered events (vs polling the system). I've already volunteered to test out patches once...

Reported in #61

> Perhaps it is worth taking the default cgroup2 root from /proc/mounts instead of using /sys/fs/cgroup by default. Oh yeah I like this idea. I'll file a separate issue for...

This sounds like a useful idea and I think it should be possible. Similar to how there's a `BaseKillPlugin`, I could see a `BaseCPlugin` providing a C interface to oomd's...

Was there a message or line number that came with the abort? I may have to rethink the async logging a bit, as log messages may not be making it...

Sorry about the spotty response time. I'm going to commit a few patches that enable inline logging (ie not async), so we can debug this better. I think we're crashing...

BTW I could not reproduce on my machine, but that doesn't surprise me. (Grumble grumble something about early stage projects)