Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!news.starlink.com!usenet From: alschnei@starlink.com (Alan Schneider) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Hints on running news under BSDI Date: Fri, 27 Oct 1995 03:31:22 GMT Organization: StarLink Internet Services Lines: 21 Message-ID: <46pmvl$7is@pegasus.starlink.com> NNTP-Posting-Host: alschnei.starlink.com X-Newsreader: Forte Free Agent 1.0.82 Thanks to Chris at BSDI for this hint... For the longest time, I kept getting a server daily run report that was over 2MB on my news server. It contained hundreds of lines of so-called 'disk errors'. I replaced the drive and got the same report stats. By default, the daily run report is done at 2am. The nightly news daemons are run at 12:01am. The problem is, the nightly expire routines do not finish on my server unitl about 3am ( we run a full news feed). While expiring, linking, and manipulating files, the daily run report kicks off and starts fsck'ing the drive. You have 2 daemons conflicting on the disk and this was causing the large 'error' reports. Anyway, all it took was to reschedule the daily run report to start at 4am. Then, they do not conflict and is able to give me an accurate daily report. Just some input for those having similar problems.