syslogd(8) with OOM Killer protection

[Jan Bramkamp]

On 27/01/16 09:27, Pavel Timofeev wrote:
> 2016-01-27 10:28 GMT+03:00 Baptiste Daroussin <bapt at 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.

I would prefer to implement the a flag keeping cron (and all other base 
system daemons) from double-forking and run it under a process 
supervisor like daemontools.