Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!newsfeed.orst.edu!newshub.tc.umn.edu!mr.net!uunet!in3.uu.net!news.alt.net!news1.alt.net!news.serv.net!not-for-mail From: zeno@serv.net (Sean T. Lamont .) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD as news-server?? Date: 17 Oct 1996 03:58:55 -0700 Organization: ServNet Internet Services, Seattle, WA Lines: 28 Message-ID: <5453hf$7n7@itchy.serv.net> References: <537ddl$3cc@amd40.wecs.org> <53ucuj$8qh@twwells.com> <543urf$ar3@flash.noc.best.net> <544bat$41o@twwells.com> NNTP-Posting-Host: itchy.serv.net In article <544bat$41o@twwells.com>, T. William Wells <bill@twwells.com> wrote: >In article <543urf$ar3@flash.noc.best.net>, >Matthew Dillon <dillon@best.com> wrote: >One other thing: you simply cannot run streaming and nonstreaming >feeds into the same server. Or, you can, but the nonstreaming >feeds will get so far behind as to be pointless. Even with fast >disks, this will be true.... this isn't my experience. we were running non-streaming nntplink to a news server that was about 30ms away from us, and we were able to keep current ; I think they have 4 or 5 other feeds. I have, however, had some problems with streaming feeds starving out nnrp connects ; it seems that these take up all of the innd process's resources and it takes a while to fork off the nnrpd's. (This problem can be fixed by running innd on a non-standard port like 118 and running in.nnrpd directly from inetd.) Your best bet of course is to stream into a feed system and not stream into a separate read system. -- Sean T. Lamont, President / Chief NetNerd, Abstract Software, Inc. (ServNet) - Internet access * WWW hosting * TCP/IP * UNIX * NEXTSTEP * WWW Development - email: lamont@abstractsoft.com WWW: http://www.serv.net "...There's no moral, it's just a lot of stuff that happens". - H. Simpson