dlucy@tropez.UUCP (Doug Lucy) (04/10/90)
Okay, what's the problem... I've just converted our news system from SCO Xenix 286 2.2 to Xenix 386 2.3.2 and have encountered news problems. After recompiling the bnews 2.11 s/w (accidentally blew it away during backup of old system) using the SCO Xenix 286 2.2 Development system and the localize.xenix shell for Xenix 2.2.3, whenever a user runs readnews, they get the following message: readnews: Active file corrupt: comp.arch 00000020001 y and sure enuf, the active file has trash in it not to mention the article numbering gets out of hand real quick. Do I need to crawl thru the bnews source (I assume inews is the culprit since postnews doesn't cause any trouble) or has someone run into this kind of thing? Anyone out there using SCO 386 OS and 286 DS ? Thanks for any and all help (wisecracks also accepted) --- "It's such a fine line between stupid..." | Doug Lucy 703.820.3922 "..and clever." | DC Pro of Falls Church, VA "Yeah, clever." | uunet!tropez!dlucy
larry@nstar.UUCP (Larry Snyder) (04/10/90)
> readnews: Active file corrupt: comp.arch 00000020001 y > I ran into the same thing. Try running expire -r, if that doesn't work - you will need to fix the file to comp.arch 0000000 0000000 y then run expire -r -- ...!iuvax!ndmath!nstar!larry -or- larry@nstar