Date: Wed, 27 Jan 2016 15:12:00 +0300 (MSK) From: Maxim Konovalov <maxim.konovalov@gmail.com> To: Pavel Timofeev <timp87@gmail.com> Cc: Baptiste Daroussin <bapt@freebsd.org>, freebsd-hackers@freebsd.org, Allan Jude <allanjude@freebsd.org> Subject: Re: syslogd(8) with OOM Killer protection Message-ID: <alpine.BSF.2.20.1601271510190.17961@mp2.macomnet.net> In-Reply-To: <CAAoTqfuVr_iXR=_AaGXTTGs20sfWeH76m3yDC-hvAL4kB9iKNA@mail.gmail.com> References: <CAOfEmZgzL2Ldu53CeSsKcUe00H1VAukhEopSUmpUK0=XAhsD1A@mail.gmail.com> <56A86D91.3040709@freebsd.org> <20160127072850.GG35911@ivaldir.etoilebsd.net> <CAAoTqfuVr_iXR=_AaGXTTGs20sfWeH76m3yDC-hvAL4kB9iKNA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[...]
> I'm one that people. I find this generilized way very usefull.
> I have least a couple of daemons that it'd never wanted to be OOMed on
> my machines. Besides syslogd, I'd protect sshd and even crond in some
> cases.
While I agree with the generalization idea via protect(1) or similar
tool just a sidenote, sshd already has this feature:
>From sshd.c:
/* Avoid killing the process in high-pressure swapping
environments. */
if (!inetd_flag && madvise(NULL, 0, MADV_PROTECT) != 0)
debug("madvise(): %.200s", strerror(errno));
--
Maxim Konovalov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1601271510190.17961>