From owner-freebsd-stable Thu Feb 18 1:53:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from frolic.no-support.loc (ppp39-85.hrz.uni-bielefeld.de [129.70.39.85]) by hub.freebsd.org (Postfix) with ESMTP id 8858310EA0 for ; Thu, 18 Feb 1999 01:53:21 -0800 (PST) (envelope-from bfischer@Techfak.Uni-Bielefeld.DE) Received: from broccoli.no-support.loc (broccoli.no-support.loc [192.168.43.99]) by frolic.no-support.loc (8.9.2/8.8.8/Debian/GNU) with ESMTP id KAA00253; Thu, 18 Feb 1999 10:50:57 +0100 (CET) From: Bjoern Fischer Received: (from bjoern@localhost) by broccoli.no-support.loc (8.9.2/8.9.2) id KAA00727; Thu, 18 Feb 1999 10:50:26 +0100 (CET) (envelope-from bjoern) Date: Thu, 18 Feb 1999 10:50:26 +0100 To: Matthew Dillon Cc: freebsd-stable@freebsd.org Subject: no dirty bufs panics any more... Message-ID: <19990218105026.A680@broccoli.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Matthew, since I stopped using an MFS as /tmp on the server, the `dirty bufs' panics on server shutdown went away. Should this give us a strong hint where to look for the errnous code? Bjoern PS: The cdda2wav problem was indeed a timing/synchronization problem. The new pre-release (in cdrecord-1.8a17) fixes this bug. It hit the net right *after* I tracked down the problem in the old code. Thank you for your help. -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UBL++++OSI++++$ P+++(-) L+++(-) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message