Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 Jan 2016 12:54:01 +0000
From:      Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com>
To:        FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: syslogd(8) with OOM Killer protection
Message-ID:  <56AE03E9.80908@NTLWorld.com>
In-Reply-To: <56A86D91.3040709@freebsd.org>
References:  <56A86D91.3040709@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Allan Jude:
 > 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.

Should all children inherit it? One of the things that the Linux OOM 
Killer does is motivated by the idea that children processes are "more 
killable" than the main service processes that spawned them; on the 
presumption that the arrangement is going to be like an SSH daemon 
spawning per-connection children, in the commonest case.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56AE03E9.80908>