Date: Wed, 27 Jan 2016 07:08:06 -0700 From: Ian Lepore <ian@freebsd.org> To: Allan Jude <allanjude@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: syslogd(8) with OOM Killer protection Message-ID: <1453903686.42081.32.camel@freebsd.org> In-Reply-To: <56A86D91.3040709@freebsd.org> References: <CAOfEmZgzL2Ldu53CeSsKcUe00H1VAukhEopSUmpUK0=XAhsD1A@mail.gmail.com> <56A86D91.3040709@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2016-01-27 at 02:11 -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. > Maybe the setting could be named *_oomprotect to make it clear what kind of protection is being configured? -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1453903686.42081.32.camel>