Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!samsung!uunet!mcsun!ukc!stl!robobar!ronald
From: ronald@robobar.co.uk (Ronald S H Khoo)
Newsgroups: news.software.b
Subject: Re: (C News) limit filesize and inews
Message-ID: <1991Jan4.115409.741@robobar.co.uk>
Date: 4 Jan 91 11:54:09 GMT
References: <27839439.1746@ics.uci.edu> <1991Jan3.214226.9184@zoo.toronto.edu>
Organization: Robobar Ltd., Perivale, Middx., ENGLAND.
Lines: 25

henry@zoo.toronto.edu (Henry Spencer) writes:

> In article <27839439.1746@ics.uci.edu> nagel@ics.uci.edu (Mark Nagel) writes:
> >...Given that this guess is correct, should relaynews ensure
> >that it's resource limitations are appropriate...
> 
> I'm not sure what the solution to this is, but contorting *every* program
> a user might invoke that might have to modify a big database is not it.

One simple fix which I'd like for other reasons (but haven't actually
bothered to implement ... sorry) would be to make inews call newsspool
instead of relaynews wouldn't it ?  (configuration option, of course,
but possibly the default one, since it's the more robust option)

Of course there will be problems for sites that turn newsrunning off
during the day.  Hmm...  It might be useful to have two separate
in.coming queues anyway, for example, if I have organisation-wide
news that needs to be run throughout the day, but usenet-wide stuff
to be only run off-peak, then you need only put the locally posted
stuff in the unaffected-by-newsrunning queue.

There is still the need to ensure that newsrun is called with the
appropriate limits raised, but you need that anyway...
-- 
ronald@robobar.co.uk +44 81 991 1142 (O) +44 71 229 7741 (H)