Xref: utzoo comp.sys.next:3675 news.software.b:3364 news.software.nntp:357
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next,news.software.b,news.software.nntp
Subject: B 2.11.17 ndbm history corruption?
Summary: it worked fine for a few weeks and then...
Message-ID: <89@toaster.SFSU.EDU>
Date: 30 Oct 89 05:58:43 GMT
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Followup-To: comp.sys.next
Organization: San Francisco State University
Lines: 24

We've been getting a small selection of newsgroups for testing,
and things seemed to be working fine, then all of a sudden
nntpxfer blew up with a segmentation violation.

I stared at it for a while, concluded that the history database
had somehow become corrupted, and did expire -R.  Things worked
ok for about 3 days.  Then it happened again.  Now it's happening
about once a day.  Is there something wrong with ndbm on NeXT 0.9?
(I've run the same netnews with dbz under System V with no problems)
Ideas?

System is NeXT 0.9, netnews B 2.11.17, NNTP 1.5.6
History contains 5539 lines.

-rw-rw-r--  1 news      355179 Oct 29 21:37 history
-rw-rw-r--  1 news        4096 Oct 29 18:00 history.dir
-rw-rw-r--  1 news      512000 Oct 29 21:37 history.pag

Filesystem    kbytes    used   avail capacity iused   ifree  %iused  Mounted on
/dev/sd1b     200670   14253  166350     8%    5236  140172     4%   /news

As you can see, we're not talking about a lot of news here.

					-=EPS=-