From owner-freebsd-hackers@freebsd.org Wed Jan 27 14:08:10 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 1AAE9A6F65E for ; Wed, 27 Jan 2016 14:08:10 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F29FD1497 for ; Wed, 27 Jan 2016 14:08:09 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Wed, 27 Jan 2016 14:09:06 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u0RE86RR031139; Wed, 27 Jan 2016 07:08:06 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1453903686.42081.32.camel@freebsd.org> Subject: Re: syslogd(8) with OOM Killer protection From: Ian Lepore To: Allan Jude , freebsd-hackers@freebsd.org Date: Wed, 27 Jan 2016 07:08:06 -0700 In-Reply-To: <56A86D91.3040709@freebsd.org> References: <56A86D91.3040709@freebsd.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 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: Wed, 27 Jan 2016 14:08:10 -0000 On Wed, 2016-01-27 at 02:11 -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. > Maybe the setting could be named *_oomprotect to make it clear what kind of protection is being configured? -- Ian