2 ms·

or use the system's oom ?

• joshAg 15d ago
  That's what's breaking the system and causing freezes. You can tune it a bit to minimize when it happens, but not get rid of the issue entirely.
• SoftTalker 15d ago
  ... which then kills sshd, locking you out of being able to get in and do any recovery.
  • nicman23 15d ago
    the system will restart sshd?
    • joshAg 15d ago
      the system will kill whatever it damn well pleases. You can tune it with priorities to ask it to try to not kill that, and once it kills your sshd once, you'll probably configure it to exempt sshd from being OOM killed at all. That doesn't fix the memory pressure or hanging or stalling, but you'll at least be able to log into the box still instead of dragging out a serial cable.
      • nicman23 13d ago
        are you using systemd or some other init ?
        • joshAg 12d ago
          both. freebsd has init scripts. ubuntu has systemd. this guide should help make it less likely for sshd or your login shell to get killed: https://ianlpaterson.com/blog/oom-lockout-ssh-survival-hardening/ https://ianlpaterson.com/blog/oom-lockout-ssh-survival-harde...
• rwmj 15d ago
  All I want is the oomkiller to always kill firefox. Somehow that's very difficult to achieve.
  • lokar 15d ago
    The oom killer is a monkey with a gun. It’s a last resort when you were going to crash (or worse, hang) anyway. You should have a much better “plan A” to avoid this situation.