Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: news.software.b
Subject: Re: B-news locking (was Duplicate articles ...)
Message-ID: <4e7136e2.1bc5b@pisa.ifs.umich.edu>
Date: 6 Dec 90 23:22:46 GMT
References: <113417@uunet.UU.NET> <1088@ai.cs.utexas.edu> <660393258.3719@proa.sv.dg.com> <15491@cs.utexas.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 13

In article <15491@cs.utexas.edu>, fletcher@cs.utexas.edu (Fletcher Mattox) writes:

  I'm concerned about the call to savehist() from insert().
  lock() doesn't protect this, as best I can tell.

The history file can't get corrupted by multiple instantiations of i/rnews,
since it only gets appended to.  The expire program makes a copy then
renames, so that isn't a problem either.

The dbm files are another matter.  Many years ago I fixed my inews to lock
the dbm files, more out of paranoia than out of any evidence of corruption.
I don't know if my fixes ever made it into the "official" sources.  I don't
run B news any more.