*BSD News Article 54951


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!in1.uu.net!newsflash.concordia.ca!sunqbc.risq.net!news.cegep-ste-foy.qc.ca!martin.cegep-ste-foy.qc.ca!user
From: mdurand@cegep-ste-foy.qc.ca (Martin Durand)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: Re: BSDI v2.0.1 with distribution innd  -> filesytem problems in daily report
Date: Tue, 14 Nov 1995 14:24:58 -0400
Organization: Cegep de Sainte-Foy
Lines: 30
Message-ID: <mdurand-1411951424580001@martin.cegep-ste-foy.qc.ca>
References: <47tgl7$e48@news.atlantech.net>
NNTP-Posting-Host: martin.cegep-ste-foy.qc.ca

In article (Dans l'article) <47tgl7$e48@news.atlantech.net>,
ramoore@atlantech.net (Randy Moore) wrote (écrivait) :

> I am running the INN version that comes with BSDI v2.0.1 
> (does anyone know for sure the version number of innd?) and 
> the daily report created by /etc/daily shows many file system 
> errors (daily reports run about 100 kbytes).  If I dismount 
> these files systems and manually run fsck, it shows no 
> problems.

I traced it back to news.daily and its run of rnews to catch up on
anything that was received while expiration and such was running. Quite
simply, rnews wasn't finished when daily began fsck'ing the drives.

Solution: fiddle with your crontab to adjust for the delays. Here's mine:
0 6 * * *       root /bin/sh /etc/daily ...
30 6 * * 6      root /bin/sh /etc/weekly ...
00 7 1 * *      root /bin/sh /etc/monthly ...

# daily cleanup and expiration
30 0 * * *       news /usr/contrib/lib/news/bin/news.daily
# process articles posted while server not answering
0 4 * * *      news /usr/contrib/lib/news/rnews -U

____________________________.________________________________________
Martin Durand               | L'imbecile n'est separe du con que par
mdurand@cegep-ste-foy.qc.ca | l'illusoire distance d'un euphemisme
Network everything          +---
Cegep de Sainte-Foy         | I know I should be working on my .sig
+1-418-659-6600 #4275       | file, but who reads these things!