Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.nla.gov.au!act.news.telstra.net!newshost.telstra.net!asstdc.scgt.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!newshost.convex.com!news.duke.edu!news.mathworks.com!newsfeed.internetmci.com!in1.uu.net!jaxnet.jaxnet.com!jax!krenaut
From: krenaut@jax.jaxnet.com (Karl Renaut)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: Re: news 'history' file is HUGE
Date: 17 Mar 1996 14:34:16 GMT
Organization: Southeast Network Services, Inc.
Lines: 43
Message-ID: <4ih7t8$h2k@jaxnet.jaxnet.com>
References: <4i34od$ctl@pegasus.starlink.com> <4i3ni6$qsu@jaxnet.jaxnet.com> <4i6te0$l7r@vanbc.wimsey.com>
NNTP-Posting-Host: jax.jaxnet.com
X-Newsreader: TIN [version 1.2 PL2]
I have limit datasize 64m and limit memoryuse 64m in my news.daily script and
yes this does speed up expire a lot! However, my comment about more
memory stands! I use every byte of my 128meg and more, its not unusual
to see 32+ megs of swap space in use. Of course, I suppose much of this
is from all the nnrpd monsters that are running!
Anybody know a technique that I could use to split the load of my news
server across multiple machines? Can I NFS mount the /var/news/spool
tree on another machine? How do large ISP's handle not only a full news
feed, but hundreds of people requesting articles?
John Henders (jhenders@wimsey.com) wrote:
: 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
--
-----------------------------------------------------------------
Karl Renaut Voice: 904-350-1969
Southeast Network Services Data: 904-292-4567
P.O. Box 56946 email: krenaut@southeast.net
Jacksonville, FL 32241 http://jax.jaxnet.com
Making Internet Affordable / - \
----------------------------------------m| o o |m----------------
U