From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 12 17:13:36 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0314D16A4CE for ; Tue, 12 Apr 2005 17:13:36 +0000 (GMT) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0633D43D41 for ; Tue, 12 Apr 2005 17:13:35 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v7.2.3.R) with ESMTP id md50001316504.msg for ; Tue, 12 Apr 2005 18:10:14 +0100 Message-ID: <020201c53f82$e4b54330$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: =?iso-8859-1?Q?=22Dag-Erling_Sm=F8rgrav=22?= References: <200504121224.j3CCOFXL019177@marlena.vvi.at> <011a01c53f66$4035aa00$b3db87d4@multiplay.co.uk> <86ll7ox7re.fsf@xps.des.no> Date: Tue, 12 Apr 2005 18:13:01 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Processed: multiplay.co.uk, Tue, 12 Apr 2005 18:10:14 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org X-MDAV-Processed: multiplay.co.uk, Tue, 12 Apr 2005 18:10:18 +0100 cc: ALeine cc: freebsd-hackers@freebsd.org Subject: Re: kernel killing processes when out of swap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 17:13:36 -0000 ----- Original Message ----- > There is no "large process detection". The first process that tries > to fault in a new page after the system runs out of swap gets killed. That makes sense. Me trying to connect to see what was going on would hence cause sshd to be killed ( not good ). It would seem that we could do with doing something to prevent this. We have had a few suggestions so far. 1. Using madvise, requires code changes per app 2. Using a sysctl to name processes which shouldn't be killed. 3. Changing how the choice of process to kill is made. I don't like the idea of having to make code changes so would vote against #1. #3 I would imagine could be quite complex and error fraught so #2 seems like the best option so far. What do others think? Go with Marc's idea? Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk.