Date: Wed, 27 Jan 2016 11:27:06 +0300 From: Pavel Timofeev <timp87@gmail.com> To: Baptiste Daroussin <bapt@freebsd.org> Cc: Allan Jude <allanjude@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: syslogd(8) with OOM Killer protection Message-ID: <CAAoTqfuVr_iXR=_AaGXTTGs20sfWeH76m3yDC-hvAL4kB9iKNA@mail.gmail.com> In-Reply-To: <20160127072850.GG35911@ivaldir.etoilebsd.net> References: <CAOfEmZgzL2Ldu53CeSsKcUe00H1VAukhEopSUmpUK0=XAhsD1A@mail.gmail.com> <56A86D91.3040709@freebsd.org> <20160127072850.GG35911@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
2016-01-27 10:28 GMT+03:00 Baptiste Daroussin <bapt@freebsd.org>: > On Wed, Jan 27, 2016 at 02:11:13AM -0500, Allan Jude wrote: >> On 2016-01-27 01:21, Marcelo Araujo wrote: >> > Hi guys, >> > >> > I would like to know your opinion about this REVIEW[1]. >> > The basic idea is protect by default the syslogd(8) against been killed by >> > OOM with an option to disable the protection. >> > >> > Some people like the idea, other people would prefer something more global >> > where we can protect any daemon by the discretion of our choice. >> > >> > Thoughts? >> > >> > >> > [1] https://reviews.freebsd.org/D4973 >> > >> > >> > Best, >> > >> >> I do like the idea of generalizing it, say via rc.subr >> >> So you can just do: >> >> someapp_protect=YES (and maybe syslogd has this enabled by default in >> /etc/defaults/rc.conf) and it prefixes the start command with protect -i. >> > I do support that idea, I think it is will be useful to more people. > > Bapt 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAoTqfuVr_iXR=_AaGXTTGs20sfWeH76m3yDC-hvAL4kB9iKNA>