From owner-freebsd-stable Mon Nov 9 11:23:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10195 for freebsd-stable-outgoing; Mon, 9 Nov 1998 11:23:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA10186 for ; Mon, 9 Nov 1998 11:23:53 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zcwuP-000393-00; Mon, 9 Nov 1998 11:23:30 -0800 Date: Mon, 9 Nov 1998 11:23:27 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Chris Williams cc: freebsd-stable@FreeBSD.ORG Subject: Re: tcpdump bringing down machine!?! In-Reply-To: <364669F0.F859EFBB@geekspace.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Nov 1998, Chris Williams wrote: > I had tcpdump running, dumping to a file on its very own seperate slice. > It apparently filled up the slice, and that slowly brought the machine > down until it rebooted itself...WHY? Probably because since tcpdump was unable to write out data, it wasn't processing new packets either. Most likely this created a backlog and ate all all your mbufs (see netstat -m). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message