Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!bcm!tmc.edu!sob
From: sob@tmc.edu (Stan Barber)
Newsgroups: news.software.b
Subject: Re: (C News) limit filesize and inews
Message-ID: <3521@gazette.bcm.tmc.edu>
Date: 8 Jan 91 19:23:27 GMT
References: <1991Jan7.182907.13583@zoo.toronto.edu> <3480@gazette.bcm.tmc.edu> <1991Jan08.180949.8613@decuac.dec.com>
Sender: usenet@bcm.tmc.edu
Organization: Baylor College of Medicine, Houston, TX
Lines: 32
Nntp-Posting-Host: tmc.edu

In article <1991Jan08.180949.8613@decuac.dec.com> mjr@hussar.dco.dec.com (Marcus J. Ranum) writes:
>sob@tmc.edu (Stan Barber) writes:
>
>>Okey, WHAT IS THE SOLUTION THEN?
>
>	Well, if you can't fix the OS, fix the code. Since Henry and Goeff
>don't want to fix it for your special case, that leaves either you fixing
>it, or your hiring or otherwise convincing someone else to fix it. Another
>alternative is to write a new news-transfer agent that works under your
>OS.

I have proposed a solution. Use the B-NEWS USG directory/file history
approach. History files are reduced in size so that the limit does not get 
reached.

Henry responds that this solution only delays the problem until some
point in the future where the amount of news history information causes 
even these files to be too large.

Another solution proposed is to write a wrapper program that executes as
root. This works, but may have security implications. It also assumes that
the news administrator has system administration authority. Something that
is often, but not always true.

I wonder how "special" my special case is. Perhaps System V-style filesize
limiting is not as widespread as I thought. I was under the impressions that
there were a bunch of 386 unix varients out there that had this stuff in in.

-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: {rutgers,mailrus}!bcm!sob   and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine