Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!umix!hyc
From: hyc@umix.cc.umich.edu (Howard Chu)
Newsgroups: news.software.b
Subject: Re: problems with rn and rrn
Message-ID: <2364@umix.cc.umich.edu>
Date: Tue, 13-Oct-87 18:04:32 EDT
Article-I.D.: umix.2364
Posted: Tue Oct 13 18:04:32 1987
Date-Received: Thu, 15-Oct-87 19:59:20 EDT
References: <1316@cartan.Berkeley.EDU> <302@ndcheg.UUCP>
Reply-To: hyc@umix.cc.umich.edu (Howard Chu)
Organization: University of Michigan Computing Center, Ann Arbor
Lines: 25
Summary: nntp sources don't coincide with rn sources
UUCP-Path: {uunet,rutgers}!umix!hyc


The basic problem is just that the released nntp sources (1.3, I think?)
were written for rn at patchlevel #29 or thereabouts, and rn is up to 39 or
40 now. I built our rrn based on a level 39 rn, and just went thru the .rej
files and applied patches by hand. (Thank god for multiple windows! Love
'dem Apollos...) It wasn't too difficult, although there are occasional
sections of code that the patches try to tweak which are completely
discarded in patchlevel 39 of rn...

I've also discovered, thru various user complaints, that the patches
provided don't change everything that can be affected by the remote server
setup. For instance, the save-article routine always invokes the saver
script with a filename of the form spooldir/news/group/article. When
using a remote rn, however, an article is always saved with the name
/tmp/rrn{pid}.{article}. Simple enough to fix, but also a rather annoying
oversight... (The saver scripts complain about the article not existing,
and then return saying the article was saved anyway. All that's saved
is 2 blank lines...) (munge up the definition of '%A' in intrp.c to take
care of this...)

Aside from these minor stumbling blocks though, I found it rather a
convenient thing to use, and have installed it successfully on Vax,
Apollo, and Sun systems...
-- 
  -- Howard Chu
	"Of *course* it's portable. It's written in C, isn't it?"