From owner-freebsd-bugs  Sat Dec 28 07:48:10 1996
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id HAA15595
          for bugs-outgoing; Sat, 28 Dec 1996 07:48:10 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA15588
          for <bugs@freebsd.org>; Sat, 28 Dec 1996 07:48:08 -0800 (PST)
Received: from critter.dk.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0ve0z2-0003wNC; Sat, 28 Dec 96 07:47 PST
Received: from critter.dk.tfs.com (localhost.dk.tfs.com [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id QAA03568; Sat, 28 Dec 1996 16:50:45 +0100 (MET)
To: dg@root.com
cc: Bruce Evans <bde@zeta.org.au>, bugs@freebsd.org
Subject: Re: another POSIX access timestamp pessimization 
In-reply-to: Your message of "Sat, 28 Dec 1996 07:00:14 PST."
             <199612281500.HAA01066@root.com> 
Date: Sat, 28 Dec 1996 16:50:44 +0100
Message-ID: <3566.851788244@critter.dk.tfs.com>
From: Poul-Henning Kamp <phk@critter.dk.tfs.com>
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199612281500.HAA01066@root.com>, David Greenman writes:
>>POSIX says that "Upon successful completion, the exec functions shall
>>mark for update the st_atime field of the file".  Not content with
>
>   In my opinion, "tough". This is one part of POSIX that I'm not interested
>in being compatible with since the cost is too great. It may not be much of
>an issue at exec time, but the disk I/O caused by the update of the access
>time that occurs later is extremely expensive.
>
>-DG

mount option ?

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@tfs.com           TRW Financial Systems, Inc.
Power and ignorance is a disgusting cocktail.