Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.14 $; site siemens.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!siemens!hartmann
From: hartmann@siemens.UUCP
Newsgroups: net.news.notes
Subject: Re: detecting problems with notesfile
Message-ID: <105100002@siemens.UUCP>
Date: Thu, 19-Sep-85 15:00:00 EDT
Article-I.D.: siemens.105100002
Posted: Thu Sep 19 15:00:00 1985
Date-Received: Fri, 20-Sep-85 06:06:21 EDT
References: <1445@rocksvax.UUCP>
Lines: 33
Nf-ID: #R:rocksvax:-144500:siemens:105100002:000:1788
Nf-From: siemens!hartmann    Sep 19 15:00:00 1985


I have been experiencing the same problem recently with our nfarchive.
The archiver tells me what it is doing in a cronlog file, so every
morning when I come in, I look at the cronlog file to make sure the
archiver ran complete.  I came in one morning to find that the archiver
had bombed out while it was archiving net.abortion.  I looked in 
net.abortion and found that the comp.* files were still there (created
by the archiver) the notesfile was closed, and there was a lock file
for it.  I opened the notesfile so it could be read, but didn't know
what to do with the rest of the mess.  I looked everywhere I could
for the source of the problem, but wasn't getting anywhere. 
This kept happening to me for about a week.  I'd come in to find that
the archiver bombed out on net.abortion again, the notesfile was
closed, and there was a lock file for it again.  At this point, 
I sent a mail message to Ray Essick asking for help.  Needless to say,
the removal of net.abortion solved all my problems.

But, just this week, I discovered that the archiver bombed out again on
net.wanted.  After going through the mess with net.abortion, I decided
to just leave the notesfile in the state it was, comp.* files present
and closed.  I was hoping to hear from Ray Essick before I tackled the
problem again.  Much to my surprise, the next morning I came in to find
that net.wanted was fixed.  There were no comp.* files, the notesfile
was open, AND the archiver had run successfully on it the previous 
evening!  What happened?  I don't know, but I DO KNOW that if I run
into this problem again, I'll leave the notesfile be and hope it
fixes itself again.  If it doesn't, then I'll worry about it.


Terri Hartmann
Siemens Research and Technology Lab
Princeton, NJ
princeton!siemens!hartmann