Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!gatech!newsfeed.internetmci.com!in2.uu.net!van-bc!news.wimsey.com!not-for-mail From: jhenders@wimsey.com (John Henders) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: news 'history' file is HUGE Date: 13 Mar 1996 08:34:08 -0800 Organization: Wimsey Information Services Lines: 21 Message-ID: <4i6te0$l7r@vanbc.wimsey.com> References: <4i34od$ctl@pegasus.starlink.com> <4i3ni6$qsu@jaxnet.jaxnet.com> NNTP-Posting-Host: vanbc.wimsey.com X-Newsreader: NN version 6.5.0 #3 (NOV) In <4i3ni6$qsu@jaxnet.jaxnet.com> krenaut@jax.jaxnet.com (Karl Renaut) writes: >As far as expire running 20 hours, you probably need more memory, I have >128megs of ram on my news server and it could still use more memory. Also, >change the time of day the the standard BSDI daily script runs so that it >runs around 5pm... the goal here is to avoid expire and the daily scripts >from running at the same time. Not necessarily more memory. As has been pointed out on the mailing list, the default user limits will constrain expire's memory usage, and cause it to us a very inefficient strategy that can account for it taking that long. The easiest solution I've found is to write a wrapper for news.daily that can be run from root's cron. I use limit datasize 95336000 and limit memoryuse 95336000 and my expire now runs quite quickly. Another thing I've found is that the new login.conf file in 2.1 affects jobs started from cron. This means that you could create a news class and open up the limits for the news user that way, but I haven't gotten around to actually trying this. -- John Henders