Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!snorkelwacker!spdcc!mirror!rayssd!anomaly!anomaly.sbs.com
From: mike@anomaly.sbs.com (Michael P. Deignan)
Newsgroups: news.software.b
Subject: INEWS's use of the link() function on multiple filesystems
Message-ID: <1925@anomaly.sbs.com>
Date: 2 Jul 90 03:09:30 GMT
Sender: mike@anomaly.sbs.com
Organization: Small Business Systems, Inc., Esmond, RI  02917
Lines: 36

I've run into an interesting problem with INEWS which I'm wondering if
anyone else has encountered.

Because of our filesystems' I-Node limit of 65500 inodes/filesystem, we
were thinking of dividing our news filesystem as follows:

	/dev/news	mount as	/usr/spool/news
	/dev/comp	mount as	/usr/spool/news/comp
	/dev/rec	mount as	/usr/spool/news/rec

This would effectively yield over 180,000 inodes for our filesystem, more
than enough to manage our 14 day expiration cycle on articles.

Unfortunately, INEWS uses the link() function, which will not work
successfully across filesystems.

Looking at the INEWS programs, there appeared to be an "artificial link()
simulator" for VMS systems, which, when utilizing the code for those
particular routines (ie: posting news) yields a "Cannot reread article"
error in ifuncs.c, in function broadcast(), at the code:

	if (hread(&h,fp, TRUE) == NULL)
		xerror("Cannot reread article");

Up to this point, it appears that fp has in fact returned a non-NULL
value.

I was wondering if anyone else has done this, or has a suggestion as to
how we might go about it...

MD
-- 
-- Michael P. Deignan, President       -- Small Business Systems, Inc. --
----------------------------------------- Box 17220, Esmond, RI  02917 --
-- Domain-Based: mike@anomaly.sbs.com  -- Voice:   +1 401 273-4669     --
-- UUCP: ...!uunet!rayssd!anomaly!mike -- Telebit: +1 401 455-0347     --