From owner-freebsd-questions Thu Feb 29 13:23:31 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.FreeBSD.org (8.7.3/8.7.3) id NAA10280 for questions-outgoing; Thu, 29 Feb 1996 13:23:31 -0800 (PST) Received: from pelican.com ([206.16.90.21]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA10255 for ; Thu, 29 Feb 1996 13:22:04 -0800 (PST) Received: by pelican.com (Smail3.1.29.1 #10) id m0tsFn1-0000SmC; Thu, 29 Feb 96 13:21 PST Message-Id: From: pete@pelican.com (Pete Carah) Subject: Re: Cnews on FreeBSD To: kline@tera.com (Gary Kline) Date: Thu, 29 Feb 1996 13:21:31 -0800 (PST) Cc: questions@freebsd.org In-Reply-To: <9602292040.AA28156@tera.com> from "Gary Kline" at Feb 29, 96 12:40:57 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-questions@freebsd.org Precedence: bulk Gary Kline writes: > Hm. I used the default//automagic install > by BSD and it stuck rnews way down within > /usr/local/libexec/news/input. Well, for the little while I ran cnews on fbsd I made it myself from Henry's distribution (with NOV added...) > This was the fault; or at least one of them. > By reading the sh scripts and reading the Taylor > docs, I'm making slow, sure progress. I'm > going to rebuild TUUCP by hand and do a custom > installation. And keep notes! Am probably > going to do the same with the Cnews installation. > The FreeBSD default is within the /usr/local > tree where the std is in /usr/lib, /usr/lib/news* > and so on. The TUUCP is fine as it comes; the cnews is the problem. (SVR4 uses the same directory setup for HDB as FBSD uses for Taylor...) The only reason to remake Taylor would be to add strange protocols. (you don't need sys file compatibility; Taylor's format is better anyhow - I went over to it on esix even...) > I used Cnews on my old 286//SVAT for 4 years; > and another 4, 5 years on ESIX, so I'm used to > whatever Henry Spencer set up. --Not /usr/local/XXXX Me too. I have replaced sendmail with smail on all my non-leaf sites (and replace sendmail.cf with one I cribbed from solaris for those :-) and the freebsd default directories for that don't work out either... (or those for INN or cnews, or apache, or...) > Clue me in if I'm wrong, but doesn't INN > mean that you've got to have a direct connect > to the net to rcv//send news? Not really but if you don't have pretty steady uucp connections it isn't worth it. (or if your feed site only batches at night like mine did for many years until they finally got more memory...) > I get my email through here at work: tera.com; > My newsfeed come via a local BBS inet outfit. > UUCP. It's ancient technology, but it works > very well for whatever, 3-11MB of news I get > a day/night. UUCP is the best thing around for multidomain mail (or multiuser mail in a single domain) on a part-time connected site;; the relevant tcp protocols all assume a full-time connection and POP3 doesn't make it, in spite of the way a lot of smaller ISPs are doing things these days. > > The "performance release" can be configured to smooth out things a bit; > > some help from your feed keeping the batch size down helps too. > > For a smaller site the memory usage of INN is a waste. > Since I'm pretty close to having Cnews working, > I'll prob'ly stick with it, but I'd like to > know about INN if it can be configured for UUCP. > At 03:45, memory isn't a major concern, :-) INN isn't worth it for that... The only advantage over Cnews is that the daemon runs all the time (meaning that once it takes up all that memory it stays...) and that nntp is integrated (in fact INN rnews is just an unbatcher that feeds into nntp). It works better for internet-connected sites or those with lots of uucp connections, so that transport is going most of the time. I feed 3 uucp sites from here with inn (and take news in from them too); it is pretty seamless, though the batchparms take some figuring out :-) -- Pete