From owner-freebsd-hackers Mon Aug 28 21:31:14 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id VAA11378 for hackers-outgoing; Mon, 28 Aug 1995 21:31:14 -0700 Received: from healer.com (healer-gw.Empire.Net [205.164.80.204]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id VAA11372 for ; Mon, 28 Aug 1995 21:31:09 -0700 Received: (from gryphon@localhost) by healer.com (8.6.11/8.6.9.1) id AAA28292; Tue, 29 Aug 1995 00:36:05 -0400 Date: Tue, 29 Aug 1995 00:36:05 -0400 From: Coranth Gryphon Message-Id: <199508290436.AAA28292@healer.com> To: freebsd-hackers@freebsd.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: Clean flag wrong in superblock Sender: hackers-owner@freebsd.org Precedence: bulk J Wunsch wrote: > It's not only the clean flag. There might be other bogus messages > resulting out of applying fsck to a live file system (incorrenct block If there is a definitive list of what is useful to warn people about (given that people who are not the sysadmin will not be reading the reports :-), let me know and I'll add that to the list of things to ignore. I've seen enough "But I *want* to see the fsck output" postings that I think it is worth the effort. > Perhaps the best solution would be to have a knob for turning it on. > I remember some Perl script called jkh who wanted to revamp all those > /etc/*ly scripts some day. :-) Funny you should mention that. I just sent Jordan a package (partially written in perl :-) which does revamp those scripts. It takes a config file, and builds the daily/weekly/monthyl scripts based upon what you want to run when. But having fsck be able to ignore the stuff that will ALWAYS show up (and can ALWAYS be safely ignored) is useful. -coranth ------------------------------------------+------------------------+ Coranth Gryphon | "Faith Manages." | | - Satai Delenn | Phone: 603-598-3440 Fax: 603-598-3430 +------------------------+ USMail: 11 Carver St, Nashua, NH 03060 Disclaimer: All these words are yours, except Europa...