Date: Wed, 27 Jan 2016 09:36:58 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Allan Jude <allanjude@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: syslogd(8) with OOM Killer protection Message-ID: <alpine.BSF.2.20.1601270932220.30320@wonkity.com> 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, 27 Jan 2016, 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. Possibly simpler to provide a list in one setting than an individual setting for each daemon. With ideas from other posters: oomprotect_daemons="crond syslogd"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1601270932220.30320>