From owner-freebsd-current Sun Apr 19 10:37:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27410 for freebsd-current-outgoing; Sun, 19 Apr 1998 10:37:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lupo.thebarn.com (lupo.lcse.umn.edu [128.101.182.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27130 for ; Sun, 19 Apr 1998 17:36:33 GMT (envelope-from cattelan@lupo.thebarn.com) Received: (from cattelan@localhost) by lupo.thebarn.com (8.8.8/8.8.8) id MAA15119; Sun, 19 Apr 1998 12:36:11 -0500 (CDT) (envelope-from cattelan) Date: Sun, 19 Apr 1998 12:36:11 -0500 (CDT) Message-Id: <199804191736.MAA15119@lupo.thebarn.com> From: Russell Cattelan MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@FreeBSD.ORG Subject: VM scrambling pages if space is exceeded X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This problem has been cropping up with "current" for about the last month. The basic problem shows up with daemon processes coreing sortly after swap space is maxed out. The most common programs: cron, sendmail and recently socks5. The main process keep running but every time it goes to fork a copy, the copy dies. I am running -current (as of Apr 14), built from scratch. Apr 19 12:03:43 lupo /kernel: swap_pager: suggest more swap space: 124 MB Apr 19 12:10:03 lupo /kernel: pid 15046 (cron), uid 0: exited on signal 11 Apr 19 12:14:27 lupo /kernel: pid 15057 (socks5), uid 0: exited on signal 11 Apr 19 12:14:50 lupo /kernel: pid 15059 (socks5), uid 0: exited on signal 11 I wasn't sure if I had bad bits at some point but I have two systems exhibiting the same behavior. -- Russell Cattelan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message