Xref: utzoo comp.bugs.sys5:406 comp.unix.microport:315 comp.unix.xenix:1780
Path: utzoo!mnetor!uunet!husc6!mit-eddie!bbn!rochester!udel!burdvax!sdcrdcf!trwrb!desint!geoff
From: geoff@desint.UUCP (Geoff Kuenning)
Newsgroups: comp.bugs.sys5,comp.unix.microport,comp.unix.xenix
Subject: Re: FIFOs and fsck
Message-ID: <1699@desint.UUCP>
Date: 25 Mar 88 06:52:36 GMT
References: <3776@chinet.UUCP> <7478@brl-smoke.ARPA> <420@vsi.UUCP>
Reply-To: geoff@desint.UUCP (Geoff Kuenning)
Distribution: na
Organization: Interrupt Technology Corp., Manhattan Beach, CA
Lines: 13

In article <420@vsi.UUCP> friedl@vsi.UUCP (Stephen J. Friedl) writes:

> Sys V fsck(1M) complains about some FIFOs -- is their any good
> reason for this?  The bummer is that it causes a laxness about
> POSSIBLE FILE SIZE ERRORS ("Oh, that's just a FIFO, don't worry
> about it") and real problems are missed.

At Callan Data Systems, Tim Smith fixed fsck to recognize FIFO's as such,
and to skip the file size error message.  Being a thorough fellow,
he also changed the final message (n files, m i-nodes, etc.) to include
"k pipes".  As I recall, he didn't find any of this very hard.
-- 
	Geoff Kuenning   geoff@ITcorp.com   {uunet,trwrb}!desint!geoff