From owner-freebsd-hackers@freebsd.org Sun Jan 31 13:35:40 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 2AA91A747E5 for ; Sun, 31 Jan 2016 13:35:40 +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 8FC778A for ; Sun, 31 Jan 2016 13:35:38 +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 Cdbd1s00v0HtmFq01dbeeu; Sun, 31 Jan 2016 13:35:38 +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=Is0Wz_cqAAAA:8 a=5hPpmlmPgHLzqOddbhoA:9 a=QEXdDO2ut3YA:10 To: FreeBSD Hackers References: <56A8B300.5080503@toco-domains.de> From: Jonathan de Boyne Pollard Subject: Re: syslogd(8) with OOM Killer protection Message-ID: <56AE0DA2.8030908@NTLWorld.com> Date: Sun, 31 Jan 2016 13:35:30 +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: <56A8B300.5080503@toco-domains.de> 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 13:35:40 -0000 Torsten Zuehlsdorff: > I would like a generalized way too. The first i thought to protect is my database. I never want to get it killed. You might enjoy this view on OOM Killers, then: * http://thoughts.davisjeff.com/2009/11/29/linux-oom-killer/ A widely circulated postgresql.service unit for systemd gained this a couple of years later: > # Due to PostgreSQL's use of shared memory, OOM killer is often overzealous in > # killing Postgres, so adjust it downward > OOMScoreAdjust=-200 Discounting 200 permil of a process' memory use, when the known problem is that that process shares a lot of its memory with its children, seems slightly conservative.