While not directly answering your question, we (facebook) use oomd[0] widely
across our fleet to solve the exact problem you have. I'd be happy to answer any
questions about it. It should (if configured correctly) be much more reliable
than
a global memory.max and less heavy handed. In theory,
I think most of us saw the situation when the system becomes
unresponsive - to a point when SSH in doesn't work - because it's out of
memory and kernel's OOM-killer doesn't kick in as fast as it should.
I have a server which from time to time - let's say once a week - is
using too much
On Sa, 16.03.19 13:27, Li Haosen (sanlis3...@gmail.com) wrote:
> hello,dear,Engineer,Forgive me,my English not good,i install ipsec and l2tp
> has some problem,i can‘t find how to solve,can help me?
Please contact the ipsec community about this, not systemd. If ipsec
fails to start like it does
On Sat, Mar 16, 2019 at 7:58 PM Manuel Reimer
wrote:
> I've found my processes:
>
> # systemctl status session-8.scope
> ● session-8.scope - Session 8 of user kodi
> Loaded: loaded (/run/systemd/transient/session-8.scope; transient)
> Transient: yes
> Active: active (running) since Sat
On Sun, Mar 17, 2019 at 12:22 AM bart schroder wrote:
> Hi Mantas,
>
Please include the mailing list when sending replies, don't turn this into
a private conversation.
>
> *Context:*
> I'm taking a Udemy course on Kafka - Kafka for Beginners.
>
> *Course Objective: Operate (Kafka)
