From owner-freebsd-arch@FreeBSD.ORG Fri May 27 13:10:16 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0F9316A41C for ; Fri, 27 May 2005 13:10:16 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DA3043D1F for ; Fri, 27 May 2005 13:10:16 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 454A11F193; Fri, 27 May 2005 15:10:15 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 1BC3B655D; Fri, 27 May 2005 15:10:15 +0200 (CEST) Date: Fri, 27 May 2005 15:10:14 +0200 From: Marc Olzheim To: Ken Smith Message-ID: <20050527131014.GA93850@stack.nl> References: <1117139065.82793.20.camel@opus.cse.buffalo.edu> <20050527091750.GB91258@stack.nl> <1117195655.88498.9.camel@opus.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline In-Reply-To: <1117195655.88498.9.camel@opus.cse.buffalo.edu> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Marc Olzheim , freebsd-arch@freebsd.org Subject: Re: Modifying file access time upon exec... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2005 13:10:16 -0000 --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 27, 2005 at 08:07:35AM -0400, Ken Smith wrote: > > I don't see any real problems with it, but perhaps people running > > executables over NFS filesystems that cannot be mounted with noatime > > might have an issue, like netbooting diskless machines... >=20 > I'm not sure why you say NFS filesystems can't be mounted with noatime. No, I'm saying that there are filesystems you wouldn't want to mount with noatime (/tmp, /var/tmp, /var/mail, /var/spool/*) because some software depends on the atime being adjusted. But atime over NFS is something you'd usually want to turn off, because it can really hurt performance. Marc --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFClxw2ezjnobFOgrERAqxXAKC7+AFrbbnRugf4YzMCyETehEQuMACeKcyM Q9oerrSRekCtKu6wLYTSO1w= =OIt6 -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY--