Path: utzoo!utstat!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!murtoa.cs.mu.oz.au!ditmela!yarra!melba.bby.oz.au!leo!gnb From: gnb@bby.oz (Gregory N. Bond) Newsgroups: news.software.b Subject: Cnews: Shouldn't expire lock out relaynews? Message-ID: Date: 30 Nov 89 02:34:23 GMT Sender: news@melba.bby.oz.au Organization: Burdett, Buckeridge and Young Ltd. Lines: 32 I just noticed an interesting thing... I was recreating our news by hand as our feed forgot about us for a few days. I had the news items in a stack of files, and was using rnews to input them. (In our system, rnews copies to in.coming and newsrun is kicked off every 20 mins by cron). The rnews eventually hung waiting for disk space. Ok, thought I, run doexpire to make some room. Half way through the doexipre, the rnews woke up (as the spool disk had emptied). That was OK. However, at 20 past, cron fired off newsrun which kicked off relaynews on the 6 or so batches waiting in in.coming. _While expire was running_. So now I think I have a corrupt history file, as the message-id from the last line in the log file appears in both history and history.o, but neither history.dir or history.pag. I got no mail from either newsrun or doexpire. Should not relaynews have waited until the expire was finished (according to my understanding of newslock()). I can verify they ran simultaneously (I was watching top(1) on the other window - a new relaynews for each batch, all the while expire was running.) Am I really hosed? What have I done wrong in the install? (This is Cnews, 13-Nov-1989, on a Sun-4 (actually, a Solbourne) running SunOs 4.0.1 and a bit). Greg. -- Gregory Bond, Burdett Buckeridge & Young Ltd, Melbourne, Australia Internet: gnb@melba.bby.oz.au non-MX: gnb%melba.bby.oz@uunet.uu.net Uucp: {uunet,pyramid,ubc-cs,ukc,mcvax,prlb2,nttlab...}!munnari!melba.bby.oz!gnb