Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site uwmacc.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!uwvax!uwmacc!bllklly From: bllklly@uwmacc.UUCP (Bill Kelly) Newsgroups: net.news.b Subject: 'Cannot install' during expire Message-ID: <413@uwmacc.UUCP> Date: Wed, 24-Oct-84 13:38:14 EDT Article-I.D.: uwmacc.413 Posted: Wed Oct 24 13:38:14 1984 Date-Received: Fri, 26-Oct-84 03:36:15 EDT Distribution: net Organization: UWisconsin-Madison Academic Comp Center Lines: 23 We've had some trouble with expire interfering with inews for incoming news from our uucp feed. Expire runs at 12:20 a.m., and sometimes overlaps with incoming news at 1:00. The news log file will indicate Cannot install article as blah, the error being that the article file already exists. The offending article file (the one that exists, but shouldn't) was created while both inews & expire were running, but didn't make it into the history file. Not suprising, I guess, since expire is rewriting the history. So is there are recommended way of keeping expire and inews from interfering? I couldn't find anything in the code to lock out incoming news or anything like that. Should this be a problem? I'm going to fake a uucp lock while expire is running if no one else has a better idea. -- Bill Kelly {allegra, ihnp4, seismo}!uwvax!uwmacc!bllklly 1210 West Dayton St/U Wisconsin Madison/Mad WI 53706 "Life's like a jigsaw...you get the straight bits, but there's plenty missing in the middle." -- Xtc