Date: Fri, 19 Nov 1999 00:31:55 -0500 (EST) From: Barrett Richardson <barrett@phoenix.aye.net> To: David G Andersen <danderse@cs.utah.edu> Cc: Matthew Dillon <dillon@apollo.backplane.com>, wes@softweyr.com, kris@hub.freebsd.org, trouble@netquick.net, freebsd-security@FreeBSD.ORG Subject: Re: secure filesystem wiping Message-ID: <Pine.BSF.4.01.9911190024440.6424-100000@phoenix.aye.net> In-Reply-To: <199911190513.WAA26469@faith.cs.utah.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 18 Nov 1999, David G Andersen wrote: > So, one side point to Wes: > > Under 3.3-STABLE (Early October), obliterate on a 141 MB file on my > machine with 148M ram managed to deadlock my system. I recall something > about a problem like this with /dev/random, so I'm sure it's cleaned up in > -current. > I just experienced something similar with 3.1. Obliterate and top don't get along it seems. Seemed to wedge, but I sat tight for a while and it came back around after a bit. I have 2 CPUs, top had one nailed to the wall, and obliterate had the other. Finally getting obliterate killed brought my system back around but top was still chunking away, screen output was froze. CPU for obliterate was froze at 50 seconds in the top screen, but it actually had several minutes. It's repeatable. - Barrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.01.9911190024440.6424-100000>