billc@wupulm.wustl.EDU (Bill Canning) (07/15/89)
I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) running on an HP 9000/360 HP-UX 6.2. Unfortunately, the Xrefs line is not keeping me from seeing the same message a number of times. I configured news to DOXREFS, and used the Configure file that came with rn. Does anyone have any suggestions? Bill Canning billc%wupulm@wupost.wustl.EDU
bbh@whizz.uucp (Bud Hovell) (07/18/89)
In article <244@wupulm.wustl.EDU> billc@wupulm.wustl.EDU (Bill Canning) writes: >I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) >running on an HP 9000/360 HP-UX 6.2. Unfortunately, the Xrefs >line is not keeping me from seeing the same message a number of >times. We have the identical problem here, and have so far been unable to find anyone who can suggest what is wrong. We just sent mail to Larry Wall to see if he can provide info as to where we messed up - haven't heard back yet. We are running unix 3.51a on an AT&T 3B1. >I configured news to DOXREFS, and used the Configure file that came >with rn. Does anyone have any suggestions? Same here. And all other features are working fine. Does anyone have any notion of what we may be going on here? Bud Hovell USENET: ...!{sun!nosun|tektronix!percival}!whizz!{bbh|postmaster|sysadmin} USPO: McCormick & Hovell, Inc., PO Box 1812, Lake Oswego, OR USA 97035 MOTD: "Vote NO!"
bill@sigma.UUCP (William Swan) (07/19/89)
In article <244@wupulm.wustl.EDU> billc@wupulm.wustl.EDU (Bill Canning) writes: >I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) >running on an HP 9000/360 HP-UX 6.2. Unfortunately, the Xrefs >line is not keeping me from seeing the same message a number of >times. >I configured news to DOXREFS, and used the Configure file that came >with rn. Does anyone have any suggestions? (I was waiting for a reply to the above, but saw none, sooo....) We, too, have this problem with rn 4.3 (patchlevel 39 or 40) and news 2.11.14 (.17?) on a vax-750 running 4.2bsd. It appeared about the same time that we installed 2.11; we'd not had the problem with 2.10.2. (Rn has not changed since long before we installed news 2.11.) I've done some hunting; the headers look fine (and the same as under news 2.10.2, w/r/t the Xrefs: line) and there's no obvious source to the problem. It's low on my list of things to fix right now, as it appears it will take me some time to hunt down. If anyone else has a pointer to the problem, though, that may change... -- Bill Swan entropy.ms.washington.edu!sigma!bill Send postal address for info: Innocent but in prison in Washington State for 13.5 years: Ms. Debbie Runyan: incarcerated 01/1989, scheduled release 07/2002. In now: 0 years, 5 months, 4 weeks, 0 days.
bart@videovax.tv.Tek.com (Bart Massey) (07/19/89)
In article <2502@sigma.UUCP> bill@sigma.UUCP (William Swan) writes: > In article <244@wupulm.wustl.EDU> billc@wupulm.wustl.EDU (Bill Canning) writes: > >I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) > >running on an HP 9000/360 HP-UX 6.2. Unfortunately, the Xrefs > >line is not keeping me from seeing the same message a number of > >times. > >I configured news to DOXREFS, and used the Configure file that came > >with rn. Does anyone have any suggestions? > > We, too, have this problem with rn 4.3 (patchlevel 39 or 40) and > news 2.11.14 (.17?) on a vax-750 running 4.2bsd. > > It appeared about the same time that we installed 2.11; we'd not had > the problem with 2.10.2. (Rn has not changed since long before we > installed news 2.11.) Try defining NORELAY in rn/config.h . The fact that one poster's problem began after 2.11 installation is a dead giveaway. The code in bits.c which implements this option (i.e. removes rn's reliance on the Relay-Version header, which disappeared as of 2.10.3) also copes with the domain portion of the hostname in the xref line. Without this option, an xref line such as Xref: videovax or.forsale:3023 tek.forsale:1881 will likely be discarded by rn, since the hostname of the system to which the article numbers refer either will not be identified or will be identified as "videovax.tv.tek.com", and so rn will think the xref line was generated on some other machine. The above explanation is admittedly incoherent, but so is the twisty code in bits.c, starting at around line 398. As always, "Use the source, Fluke" :-), and good luck! Bart Massey ..tektronix!videovax.tv.tek.com!bart ..tektronix!reed.bitnet!bart
tim@attdso.att.com (Tim J Ihde) (07/19/89)
In article <2502@sigma.UUCP> bill@sigma.UUCP (William Swan) writes: >In article <244@wupulm.wustl.EDU> billc@wupulm.wustl.EDU (Bill Canning) writes: >>I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) >>running on an HP 9000/360 HP-UX 6.2. Unfortunately, the Xrefs >>line is not keeping me from seeing the same message a number of >>times. > >(I was waiting for a reply to the above, but saw none, sooo....) Me too. I got this fixed at our site over a year ago, and I'm trying to remember what I did. It has to do with the way the Xrefs lines work. Xrefs not only lists article numbers, but also your machine name; and I think your rn is thinking that this is not the right machine name so it ignores the references. Is that vague enough? Sorry I can't remember any better. An extra tip: I'm quite sure I found the problem using the -D debug mode of rn. tim -- Tim J Ihde INTERNET: tim@attdso.att.com (201) 898-6687 UUCP: att!attdso!tim
jbuck@epimass.EPI.COM (Joe Buck) (07/20/89)
In article <2502@sigma.UUCP> bill@sigma.UUCP (William Swan) writes: >>I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) >>running on an HP 9000/360 HP-UX 6.2. Unfortunately, the Xrefs >>line is not keeping me from seeing the same message a number of >>times. I assume you mean the reverse, 2.11 (patch level 14) and news 2.11, patch level 34. I've saved all the rn patches; rn must be patched to at least level 29 for DOXREFS to work with 2.11. See the notes below too. In article <244@wupulm.wustl.EDU> billc@wupulm.wustl.EDU (Bill Canning) writes: >We, too, have this problem with rn 4.3 (patchlevel 39 or 40) and >news 2.11.14 (.17?) on a vax-750 running 4.2bsd. > >It appeared about the same time that we installed 2.11; we'd not had >the problem with 2.10.2. (Rn has not changed since long before we >installed news 2.11.) Rerun rn's Configure script. In answer to the question, Are you running 2.10.3 or above? Answer "yes". rn used to do Xref: processing by means of an algorithm that uses the Relay-Version header, which was in 2.10.2 but no longer exists. This will fix your problem. -- -- Joe Buck jbuck@epimass.epi.com, uunet!epimass.epi.com!jbuck
bill@sigma.UUCP (William Swan) (07/20/89)
In article <5484@videovax.tv.Tek.com> bart@videovax.tv.tek.com (Bart Massey) writes: }>>I have rn 4.3 (...) and news 2.11 (...) Unfortunately, the Xrefs }>>line is not keeping me from seeing the same message a number of times. }>>I configured news to DOXREFS, and used the Configure file that came }>>with rn. Does anyone have any suggestions? }Try defining NORELAY in rn/config.h . The fact that one poster's problem }began after 2.11 installation is a dead giveaway. I tried this change and it works perfectly! Many thanks!!! -- Bill Swan entropy.ms.washington.edu!sigma!bill Send postal address for info: Innocent but in prison in Washington State for 13.5 years: Ms. Debbie Runyan: incarcerated 01/1989, scheduled release 07/2002. In now: 0 years, 5 months, 4 weeks, 1 day.
dan@sparkles.dcss.mcmaster.ca (Dan Trottier) (07/20/89)
In article <5484@videovax.tv.Tek.com> bart@videovax.tv.tek.com (Bart Massey) writes: >> In article <244@wupulm.wustl.EDU> billc@wupulm.wustl.EDU (Bill Canning) writes: >> >I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) >> >running on an HP 9000/360 HP-UX 6.2. Unfortunately, the Xrefs >> >line is not keeping me from seeing the same message a number of >> >times. >> >I configured news to DOXREFS, and used the Configure file that came >> >with rn. Does anyone have any suggestions? >> >The code in bits.c which implements this option (i.e. removes rn's reliance >on the Relay-Version header, which disappeared as of 2.10.3) also copes with >the domain portion of the hostname in the xref line. Without this option, >an xref line such as > Xref: videovax or.forsale:3023 tek.forsale:1881 >will likely be discarded by rn, since the hostname of the system to which >the article numbers refer either will not be identified or will be >identified as "videovax.tv.tek.com", and so rn will think the xref line >was generated on some other machine. This symptom of not doing Xrefs properly shows up when reading news over and nfs mount. The Xrefs line will have the name of the news server but rn will check that name against the name of the local host. The ideal fix is to edit bits.c and have chase_xrefs look for a file called /usr/lib/news/nfshostname (Bnews 2.11) or /usr/lib/news/server (Cnews 1.0). If that file exists then it is likely that your news directories are mounted from a server and you need to read the name from the file. That name should be checked against the name in the Xrefs line. -- Dan Trottier dan@maccs.McMaster.CA Dept of Computer Science ...!uunet!utai!utgpu!maccs!dan McMaster University (416) 525-9140 x3444
news@amms4.UUCP (news administration) (07/20/89)
In article <2502@sigma.UUCP> bill@sigma.UUCP (William Swan) writes: >In article <244@wupulm.wustl.EDU> billc@wupulm.wustl.EDU (Bill Canning) writes: >>I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) >>running on an HP 9000/360 HP-UX 6.2. Unfortunately, the Xrefs >>line is not keeping me from seeing the same message a number of >>times. >>I configured news to DOXREFS, and used the Configure file that came >>with rn. Does anyone have any suggestions? >(I was waiting for a reply to the above, but saw none, sooo....) Me too! Me too! We, also have this problem. Our environment is: rn 4.3 (patchlevel 40) and news 2.11.14 on a Plexus P/75 running vanilla UNIX System 5 Release 2 Any thoughts would be appreciated! Cheers, -- Harry Gross | reserved for | something really Internet: hjg@amms4.UUCP (we're working on registering)| clever - any UUCP: {jyacc, rna, bklyncis}!amms4!hjg | suggestions?
billc@wupulm.wustl.EDU (Bill Canning) (07/21/89)
Thanks to everyone who responded. I think the problem was that patch29 for rn had a problem, and several things in bits.c did not get changed. This caused a problem in future patches to bits.c, and so I had to patch this file by hand, according to the *.rej files. When I got the file up to patchlevel 40 and compiled it, everything worked fine. Now all that remains is to figure out why patch didn't work on the package, but that's a topic for another newsgroup. Thanks again, Bill Canning billc%wupulm@wupost.wustl.EDU -- Bill Canning billc%wupulm@wupost.wustl.EDU
hjg@amms4.UUCP (Harry Gross) (07/25/89)
In article <595@amms4.UUCP> I wrote >In article <2502@sigma.UUCP> bill@sigma.UUCP (William Swan) writes: >>In article <244@wupulm.wustl.EDU> billc@wupulm.wustl.EDU (Bill Canning) writes: >>>I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) >>>running on an HP 9000/360 HP-UX 6.2. Unfortunately, the Xrefs >>>line is not keeping me from seeing the same message a number of >>>times. >>>I configured news to DOXREFS, and used the Configure file that came >>>with rn. Does anyone have any suggestions? >>(I was waiting for a reply to the above, but saw none, sooo....) >Me too! Me too! >We, also have this problem. Our environment is: > rn 4.3 (patchlevel 40) and news 2.11.14 on a Plexus > P/75 running vanilla UNIX System 5 Release 2 >Any thoughts would be appreciated! I received a couple of mail responses to this (Thanks to all who replied - a disk space problem resulted in my loosing your notes, so I can't thank you specifically - sorry :-) It was pointed out that the NORELAY flag must be defined in config.h for cross-referencing to work properly. I looked back at my source installation and sure enough, it wasn't. I did a little investigation, and found the problem to be in patch29 to the news software. It seems that some site somewhere munged the file slightly, resulting in the patch not being fully applied. There was a note in the beginning of the patch, however, that addressed this problem (apparently some others had experienced messed up patches earlier on - I didn't :-), stating to run patch with the -l flag. When I originally installed rn, I had created a script to apply all the patches automatically, and didn't catch the error. When I redid everything by hand, patch29 failed to update Configure and bits.c properly. I reversed the patches, and reapplied them using patch -l, and they went in just fine. NOW IT WORKS!! Hooray for the good guys. To Bill Canning, who wrote: >>>I have rn 4.3 (patch level 14) and news 2.11 (patch level 34(?)) I think you mean rn 4.3 patch level 34 and news 2.11 patch level 14 (at least I hope so, as there are only 17 available patches to news 2.11 :-) Try my above fix and see if it solves your problems. Likewise to William Swan. Cheers -- Harry Gross | reserved for | something really Internet: hjg@amms4.UUCP (we're working on registering)| clever - any UUCP: {jyacc, rna, bklyncis}!amms4!hjg | suggestions?