Xref: utzoo comp.unix.sysv386:4072 news.software.b:6630
Newsgroups: comp.unix.sysv386,news.software.b
Path: utzoo!telly!eci386!woods
From: woods@eci386.uucp (Greg A. Woods)
Subject: Re: The INfamous inode bug
Message-ID: <1991Jan15.201410.18885@eci386.uucp>
Reply-To: woods@eci386.UUCP (Greg A. Woods)
Organization: Elegant Communications, Inc.
References: <5685@rsiatl.Dixie.Com> <53@esacs.UUCP> <1991Jan12.025119.27665@nuchat.sccsi.com> <114@thor.UUCP>
Date: Tue, 15 Jan 91 20:14:10 GMT

In article <114@thor.UUCP> scjones@thor.UUCP (Larry Jones) writes:
> Your have a valid point, but at least Interactive TRIED to fix the
> problem.  AT&T has known about this bug for heaven-only-knows how
> long and they've just finally gotten around to fixing it for R4.
> And who knows if their fix is really right or not?!?

Then again, those of us who do the old resource utilization
calculations and predictions never exercise the bug in the first
place.  Even with a 100 Mb news spool I've never run out of inodes,
and thus I don't know if any system I use has ever had the bug!

Careful tuning of the news software will also usually prevent you from
even running out of blocks.  Further checks can prevent you from ever
running out of inodes too.
-- 
							Greg A. Woods
woods@{eci386,gate,robohack,ontmoh,tmsoft}.UUCP		ECI and UniForum Canada
+1-416-443-1734 [h]  +1-416-595-5425 [w]  VE3TCP	Toronto, Ontario CANADA
Political speech and writing are largely the defense of the indefensible-ORWELL