From owner-freebsd-current Tue Apr 21 11:23:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06660 for freebsd-current-outgoing; Tue, 21 Apr 1998 11:23:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06546 for ; Tue, 21 Apr 1998 18:22:59 GMT (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id OAA28180; Tue, 21 Apr 1998 14:22:54 -0400 (EDT) (envelope-from wollman) Date: Tue, 21 Apr 1998 14:22:54 -0400 (EDT) From: Garrett Wollman Message-Id: <199804211822.OAA28180@khavrinen.lcs.mit.edu> To: Russell Cattelan Cc: freebsd-current@FreeBSD.ORG Subject: VM scrambling pages if space is exceeded In-Reply-To: <199804191736.MAA15119@lupo.thebarn.com> References: <199804191736.MAA15119@lupo.thebarn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > 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. I noticed this on my news transit box. I also noticed that my news spool files are getting corrupted (with strings of nulls being inserted at inopportune times). For the moment it's not too bad (I think), but I'm dropping those articles, and would rather not be. (I just turned off Perl filters to see if that has any effect.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message