Xref: utzoo news.software.b:7344 news.admin:13079 comp.unix.sysv386:6571
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!unmvax!uokmax!servalan!rmtodd
From: rmtodd@servalan.uucp (Richard Todd)
Newsgroups: news.software.b,news.admin,comp.unix.sysv386
Subject: Re: Problem with C news under ISC 1.0.6 with history file size
Message-ID: <1991Apr3.040838.681@servalan.uucp>
Date: 3 Apr 91 04:08:38 GMT
References: <1991Apr2.174523.1204@sci34hub.sci.com>
Organization: Ministry of Silly Walks
Lines: 26

gary@sci34hub.sci.com (Gary Heston) writes:

>I've run into a problem the last couple of days. C news is tossing every
>batch with a "unable to write history file" error (in errlog). My first
>guess at the reason is the good 'ole ulimit--history is now 8388608 bytes
>in size. 
...
>I'd really rather not have C news running as root; while it's fine 
>software, it shouldn't be necessary to do that because of an OS 
>shortcoming. I have, in the past, conducted a couple of extensive 
>searches for upping ulimits' default, without success (we have
>a system in another plant with the same problem, with a large database).

Hmm.  There's a good chance that one little piece of C News on your system
is *already* running as root -- the setnewsids program, which is used for
setting euids and such correctly for the benefit of relaynews, and is 
definitely needed on some SysV systems.  setnewsids is a "wrapper" that
relaynews executes when it finds it has the wrong permissions, and after
things get set right, re-execs relaynews.  Since setnewsids runs setuid-root,
you can stick the ulimit() in there; I seem to recall someone else with
a SysV with stupidly low, non-configurable default ulimit mentioning that 
he did this.  You might try this.  
--
Richard Todd	rmtodd@uokmax.ecn.uoknor.edu  rmtodd@chinet.chi.il.us
	rmtodd@servalan.uucp
"Elvis has left Bettendorf!"