From owner-freebsd-hackers Fri Jul 28 10:52:49 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id KAA21417 for hackers-outgoing; Fri, 28 Jul 1995 10:52:49 -0700 Received: from pht.com (exodus.pht.com [198.60.59.99]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id KAA21409 for ; Fri, 28 Jul 1995 10:52:46 -0700 Received: by pht.com id AA08101 (5.67b/IDA-1.5 for hackers@freebsd.org); Fri, 28 Jul 1995 10:16:36 -0600 Date: Fri, 28 Jul 1995 10:16:34 -0600 (MDT) From: Brad Midgley To: hackers@freebsd.org Subject: amd and keeping filesystems r/o Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@freebsd.org Precedence: bulk With 22 gigs of file systems connected to our freebsd machine, crashing and having to fsck them all is quite a pain. LFS is a solution in the long term, but in the mean time is it possible to set up something like amd to keep file systems read-only until a write access is attempted and then put them back into read-only after some delay? as I'm doing a lot of unscheduled rebooting :) lately, I've just been making everything I can read-only (by hand). I was even thinking of an ugly solution like a crontab entry to make our ftp mirror archives r/w only during the mirroring window. yick. would amd help?