Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!rochester!kodak!ispd-newsserver!ism.isc.com!bomber.ism.isc.com!support
From: support@bomber.ism.isc.com (Support Account)
Newsgroups: comp.unix.sysv386
Subject: Re: The INfamous inode bug
Message-ID: <1991Jan10.161022.3360@ism.isc.com>
Date: 10 Jan 91 16:10:22 GMT
References: <PETE.90Dec25124943@fidata.fi> <43@esacs.UUCP> <PETE.91Jan4001907@fidata.fi> <45@esacs.UUCP> <5685@rsiatl.Dixie.Com> <53@esacs.UUCP>
Sender: usenet@ism.isc.com (Usenet News)
Reply-To: support@bomber.ism.isc.com (Support Account)
Organization: Interactive Systems Corp., Santa Monica, CA
Lines: 14

In article <53@esacs.UUCP> pizzi@esacs.UUCP (Riccardo Pizzi) writes:
>What news package are you running? Maybe this makes a difference.
>I would like to hear from ISC support about the bug status (I run 2.2).
>

Code was added/fixed in V2.2 of Interactive Unix which resolved
all the instances of the inode problem Interactive could test
internally. Recently, another situation which generates the bug
was discovered, which was not tested for, and which is being
fixed. There is no date when this fix will be available, but
it is possible it will be in Interactive Unix V2.3.


...