Thread View: oh.news
2 messages
2 total messages
Started by Doug Sewell
Tue, 03 Nov 1992 14:40
INN experiences ?
Author: Doug Sewell
Date: Tue, 03 Nov 1992 14:40
Date: Tue, 03 Nov 1992 14:40
49 lines
2880 bytes
2880 bytes
We might well be buying a new Sun (32MB/1.3GB IPC) to run usenet on, to replace our current and failing NCR Tower. My question is: should I in- stall C-News/NNTP/nntplink, or INN ? Since I'm starting from scratch, this is the ideal time to change if I'm going to. I will be able to have both machines up the same time, and both machines are dedicated to news. My environment: Three "busy" newsfeeds half-a-dozen trivial ones. All of my newsfeeds have read access as well, but only one actually uses it (their software will have to be modified to issue a MODE READER). I also have a trivial UUCP MSDOS Waffle connection for my home system. Six NNTPLINK outgoing newsfeeds and half-a-dozen or so trivial ones that are currently sent with nntpxmit. Some of my incoming or outgoing feeds are running non-Unix news software - some are running VM with NNTPRCVR/NNTPXMIT/PSU NetNews, one is running a full VM NNTPD (!) and NNTPXMIT, and a VMS system running ANU News. Typically I have 2-3 transfer daemons and as many as 15 reader/poster daemons at a time. This includes a few off-campus readers from sites that are too small to run their own server, and the Youngstown Free-Net sig and usenet readers (our biggest single "customer"). All reading is done via NNTP right now, since our current server doesn't support NFS. Our newsreaders are tin, xrn, nnr (VM), and probably a copy or two of rrn or gnus, and the FreePort newsreader (nr/mgnr). I don't maintain xrn, rrn, or gnus, because they're run on the Math/CS systems. My thoughts: I'm comfortable with C-News/NNTP/nntplink, but pretty adaptable. In addition, I know of two sites in Ohio running INN (zaphod and CWRU). I don't run any of the performance patches (daemon relaynews, msgidd, etc) because support for them is harder to get, and the one that would help me most (msgidd) won't run on our current machine (no unix domain sockets). INN is attractive because it's one package, and can't get out-of-sync like C-News and NNTP did when the change to relative pathnames came. I also like the synchronous posting, and the I-O improvements. Comments ? -- Doug Sewell, Tech Support, Computer Center, Youngstown State University doug@cc.ysu.edu doug@ysub.bitnet <internet>!cc.ysu.edu!doug "Recession: your friend loses his job. Depression: you lose your job. Recovery: Bush loses his job" - Bill Davidsen
Re: INN experiences ?
Author: Stephen Williams
Date: Tue, 10 Nov 1992 18:25
Date: Tue, 10 Nov 1992 18:25
25 lines
1552 bytes
1552 bytes
doug@cc.ysu.edu (Doug Sewell) writes: : We might well be buying a new Sun (32MB/1.3GB IPC) to run usenet on, to : replace our current and failing NCR Tower. My question is: should I in- : stall C-News/NNTP/nntplink, or INN ? Since I'm starting from scratch, : this is the ideal time to change if I'm going to. I will be able to have : both machines up the same time, and both machines are dedicated to news. : : My environment: : : Three "busy" newsfeeds half-a-dozen trivial ones. All of my newsfeeds have ... : like C-News and NNTP did when the change to relative pathnames came. I : also like the synchronous posting, and the I-O improvements. : : Comments ? I love it. I also have added zoo archiving of online-articles to cut inodes and space usage. My changes are not fully debugged however. Watch comp.news.nntp.... sdw -- Stephen D. Williams Local Internet Gateway Co.; SDW Systems 513 496-5223APager LIG dev./sales Internet: sdw@world.std.com CIS 76244.210@compuserve.com OO R&D Source Dist. By Horse: 10028 Village Tree Ct., Miamisburg, OH 45342 GNU Support ICBM: 39 34N 85 15W I love it when a plan comes together
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads