From owner-freebsd-hackers@freebsd.org Sun Jan 31 12:55:21 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95CE2A7373B for ; Sun, 31 Jan 2016 12:55:21 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from know-smtprelay-omc-3.server.virginmedia.net (know-smtprelay-omc-3.server.virginmedia.net [80.0.253.67]) by mx1.freebsd.org (Postfix) with ESMTP id 07DC69D5 for ; Sun, 31 Jan 2016 12:55:20 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from [192.168.1.100] ([86.10.211.13]) by know-smtprelay-3-imp with bizsmtp id Ccu91s00Z0HtmFq01cu9WS; Sun, 31 Jan 2016 12:54:09 +0000 X-Originating-IP: [86.10.211.13] X-Spam: 0 X-Authority: v=2.1 cv=MtevkDue c=1 sm=1 tr=0 a=SB7hr1IvJSWWr45F2gQiKw==:117 a=SB7hr1IvJSWWr45F2gQiKw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=vNiBO2GyW91VwNN-wXkA:9 a=QEXdDO2ut3YA:10 To: FreeBSD Hackers References: <56A86D91.3040709@freebsd.org> From: Jonathan de Boyne Pollard Subject: Re: syslogd(8) with OOM Killer protection Message-ID: <56AE03E9.80908@NTLWorld.com> Date: Sun, 31 Jan 2016 12:54:01 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <56A86D91.3040709@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2016 12:55:21 -0000 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.