Date: Wed, 27 Jan 2016 17:48:00 +0100 From: Torsten Zuehlsdorff <mailinglists@toco-domains.de> To: freebsd-hackers@freebsd.org Subject: Re: syslogd(8) with OOM Killer protection Message-ID: <56A8F4C0.9090200@toco-domains.de> In-Reply-To: <alpine.BSF.2.20.1601270932220.30320@wonkity.com> References: <CAOfEmZgzL2Ldu53CeSsKcUe00H1VAukhEopSUmpUK0=XAhsD1A@mail.gmail.com> <56A86D91.3040709@freebsd.org> <alpine.BSF.2.20.1601270932220.30320@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27.01.2016 17:36, Warren Block wrote: >>> 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" I like this approach! Greetings, Torsten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56A8F4C0.9090200>