holloway@drivax.UUCP (01/22/87)
I don't say 'bugs', because I know that these features are working... they just aren't working NOW. On OUR system. And we need some help. 1) Reading 1 copy of a cross-posted article. Somebody else on the net had the problem after they converted to the new inews program, and just reConfigured rn and it started working. That doesn't do the trick here. What part of the code skips already read articles? How does it know? 2) Prompting for new newsgroups. This is something that worked before we went to the new mail system. But now, the system occasionally prompts about new newsgroups, but often doesn't. This is supposed to work off changes in the active file size, right? -- ....!ucbvax!hplabs!amdahl!drivax!holloway My balogna has a first name, it's Jimbob. My balogna has a second name, it's Boltwangle. But it prefers to be called Jim.
lwall@sdcrdcf.UUCP (01/26/87)
In article <807@drivax.UUCP> holloway@drivax.UUCP (Bruce Holloway) writes: >1) Reading 1 copy of a cross-posted article. > Somebody else on the net had the problem after they converted to the new > inews program, and just reConfigured rn and it started working. > > That doesn't do the trick here. What part of the code skips already > read articles? How does it know? Patch #29 fixed this. You need to have installed this before running Configure. If you're lazy, don't rerun Configure, just add #define NORELAY to config.h. By the way, the patchlevel of a fully patched rn is 39. >2) Prompting for new newsgroups. > > This is something that worked before we went to the new mail system. But > now, the system occasionally prompts about new newsgroups, but often > doesn't. > > This is supposed to work off changes in the active file size, right? Right. There are other things that need to be true for a newsgroup to be counted as new as well, having to do with the last modification date of either article 1, or of the directory if there are no articles. What it does if there is no directory I'm not sure, but I think it would ignore it until the directory is created. Maybe this is what you are noticing. Larry Wall {allegra,burdvax,cbosgd,hplabs,ihnp4,sdcsvax}!sdcrdcf!lwall
jef@unisoft.UUCP (01/27/87)
There is definitely a problem with asking about new groups. It seems
that if I run rn between the time that the newgroup message arrives
and the time that the first real message arrives (which can be a matter
of days), rn tells me "foo does not exist" and I never get asked whether
I want to add it, even later when it "exists".
By the way, is there a better place than this for reporting rn bugs?
Cause I've got a couple more.
---
Jef
Jef Poskanzer unisoft!jef@ucbvax.Berkeley.Edu ...ucbvax!unisoft!jef
"59. I do not!"henry@garp.UUCP (01/27/87)
And (as long as we're on this topic) how can one get the latest copy
of rn? (one with all thirty-some-odd patches applied, that is ...)
The copy I'm using is of dubious origin, and finding the latest copy
would leave me with something that I know about.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Henry Mensch <henry@garp.mit.edu>
{ames,cca,rochester,mit-eddie}!garp!henrylwall@sdcrdcf.UUCP (01/27/87)
In article <240@unisoft.UUCP> jef@unisoft.UUCP (Jef Poskanzer) writes: >There is definitely a problem with asking about new groups. It seems >that if I run rn between the time that the newgroup message arrives >and the time that the first real message arrives (which can be a matter >of days), rn tells me "foo does not exist" and I never get asked whether >I want to add it, even later when it "exists". This was fixed in patch #28, way back in July. The current patchlevel of rn is #40. Where've you been? >By the way, is there a better place than this for reporting rn bugs? >Cause I've got a couple more. Yeah, like, to me, gag me with a soap opera. Larry Wall {allegra,burdvax,cbosgd,hplabs,ihnp4,sdcsvax}!sdcrdcf!lwall P.S. Here's the current index of rn patches: 1: backpage can confuse header parser resulting in bad reply address 2: KILL file can set art < absfirst, causing "(-1 more)" error 3: search commands shouldn't report things junked that already were 4: there should be a way to suppress quoted material and signatures 5: after exiting newsgroup with 'Q', space won't reenter newsgroup 6: devtty isn't defined for TERMIO systems 7: various fixes for configure and make stuff 8: default doesn't work in normal vs mailbox question 9: some random typos and stuff 10: 7 with one blow 11: mbox and norm.saver don't put "Article n of newsgroup" line. 12: Rnmail shouldn't ask editor if EDITOR or VISUAL defined 13: Configure gets spoofed on terminfo vs. termlib. 14: rn -c speedup 15: shouldn't have included sys/types.h twice 16: filexp feeds confusing command to sed 17: articles which are subdirectories should really be ignored 18: The 'r' and 'f' commands ought to work from "End of newsgroup" 19: on some systems rn can miss new newsgroups 20: kill files are boring at low speed 21: %d that should be %ld 22: Patch #14 causes malloc mixups on "rn -c" 23: the NOLINEBUF option doesn't work 24: tailorable mail call string 25: various Pnews and Rnmail upgrades. 26: Catch command can throw off unread article count 27: %m upgrade 28: Won't add new newsgroups that don't have a spool directory yet. 29: Xrefs don't work in 2.10.3 30: changes for compatibility with newsgroup renaming 31: Number of new articles arriving is miscalculated 32: KILL on newly arrived articles can accidentally mark articles read 33: The net reorganization may make too many newsgroups for rn to handle 34: Patch #32 was incomplete. 35: rn -c can produce a memory fault 36: Rn can dump core on 16 bit machines 37: Rn dumps core on appending line to .newsrc 38: Rn dumps core on 16 bit USG machines 39: patch #37 deletes the .rnlast file 40: moderated groups work differently now
tank@apc3b2.UUCP (01/28/87)
oops.... didn't know this is what a followup did.... -tank-
davids@iscuva.UUCP (David Schmidt) (01/31/87)
In article <653@mit-amt.MEDIA.MIT.EDU> henry@garp.UUCP (Henry Mensch) writes: >And (as long as we're on this topic) how can one get the latest copy >of rn? (one with all thirty-some-odd patches applied, that is ...) >The copy I'm using is of dubious origin, and finding the latest copy >would leave me with something that I know about. With all the requests for rn, and all the confusion about what patch level it's at, maybe it's time to update the version number of rn to 4.4 and post it to the net again. I personally have the current version (with all patches) but I had to work a while to find it. I'm sure others would appreciate this. -- David Schmidt UUCP: ihnp4!tektronix!reed!iscuva!davids ISC Systems Corp. Phone: (509)927-5479 Box TAF-C8 Spokane, WA 99220