This is B-2.11.17-ndbm-history-corruption? in view mode; [Up]
Date: Sun 30-Oct-1989 05:58:43 From: Unknown Subject: B 2.11.17 ndbm history corruption? 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=- >From: epsilon@wet.UUCP (Eric P. Scott)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.