From owner-freebsd-hackers Fri Jan 10 01:01:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA00920 for hackers-outgoing; Fri, 10 Jan 1997 01:01:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA00915 for ; Fri, 10 Jan 1997 01:01:21 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA24600 for hackers@FreeBSD.ORG; Fri, 10 Jan 1997 09:58:41 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id JAA22586; Fri, 10 Jan 1997 09:35:36 +0100 (MET) Message-ID: Date: Fri, 10 Jan 1997 09:35:35 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: mount w/ noatime option References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from The Hermit Hacker on Jan 9, 1997 17:53:22 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As The Hermit Hacker wrote: > With all the talk about the noatime option, I figured I'd see > what happens if I used mount from -current (3.0) on my 2.2 machine, > since /usr/include/sys/mount.h defines MNT_NOATIME... > > It worked, but I'm wondering if this is "A Bad Thing"...like, It's not a Bad Thing per se, but i think it violates Posix. You normally probably would like to keep the atime record, so you can e.g. wipe out files from tmp areas nobody ever had a look at since several days. You don't win much by not bumping the atime, except in some situations like a newsserver -- but there, you win a lot. That's why the option is there. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)