From owner-freebsd-current Thu Sep 24 18:57:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03532 for freebsd-current-outgoing; Thu, 24 Sep 1998 18:57:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03491 for ; Thu, 24 Sep 1998 18:56:44 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id LAA00448 for ; Fri, 25 Sep 1998 11:26:35 +0930 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA03382; Fri, 25 Sep 1998 11:26:34 +0930 Date: Fri, 25 Sep 1998 11:26:34 +0930 (CST) From: Kris Kennaway To: current@FreeBSD.ORG Subject: VM out-of-swap problems Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone actively working on the problems related to daemons dying after the system has used a large amount of swap (the old "inetd() in realloc: junk pointer" thing)? It seems to me that with the release just around the corner this is something which should be killed now, as it seems to be an easily repeatable problem for many people and would adversely impact many servers in the real world (e.g. potential DoS risk). If no-one has the time to look at this in their spare time, may I suggest to Jordan that he look at paying one of the VM experts (John Dyson?) to fix this problem before 3.0 rolls out the door? I am quite willing to run debugging patches if someone provides them to track down the problem, since I can repeat it quite easily over here (well, I haven't seen it since I allocated that extra 140MB of swap space, but I havent heard any reasons to believe the problem is gone without it). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message