From owner-freebsd-stable Thu Feb 11 12:19:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11302 for freebsd-stable-outgoing; Thu, 11 Feb 1999 12:19:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11296 for ; Thu, 11 Feb 1999 12:19:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id MAA94489; Thu, 11 Feb 1999 12:19:11 -0800 (PST) (envelope-from dillon) Date: Thu, 11 Feb 1999 12:19:11 -0800 (PST) From: Matthew Dillon Message-Id: <199902112019.MAA94489@apollo.backplane.com> To: Bjoern Fischer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS + cdda2wav References: <19990209233951.A402@broccoli.no-support.loc> <199902100355.TAA77997@apollo.backplane.com> <19990211031636.A2690@broccoli.no-support.loc> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Then I compiled the whole thing for debugging. Synchronization :between the parent (writing) process and the child (reading) :process is managed with fifos. Just before the last write should :be done the syncing function receives a SIGPIPE as it was trying :to write to the pipe. At the time I don't know how this can happen. : : Bjoern SIGPIPE occurs if the reader side of the fifo goes away and the writer then tries to write. So it looks like one of the two processes must be dying ( perhaps thinking that the transfer is done ) whe, in fact, there is still a little more data in the fifo to write. It sounds like a timing bug in the program rather then an OS bug. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message