Xref: utzoo comp.protocols.nfs:2321 comp.sys.sgi:10134
Newsgroups: comp.protocols.nfs,comp.sys.sgi
Path: utzoo!utgpu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!aurora.physics.utoronto.ca!sysmark
From: sysmark@aurora.physics.utoronto.ca (Mark Bartelt)
Subject: Re: NFS atime (non-)update
Message-ID: <1991May16.121828.14206@helios.physics.utoronto.ca>
Followup-To: comp.protocols.nfs
Sender: news@helios.physics.utoronto.ca (News Administrator)
Nntp-Posting-Host: aurora.physics.utoronto.ca
Reply-To: mark@cita.toronto.edu
Organization: University of Toronto Physics/Astronomy/CITA
References: <1991May16.112349.13681@helios.physics.utoronto.ca>
Date: Thu, 16 May 1991 12:18:28 GMT

Upon rereading the above-referenced article which I posted earlier
today, I notice that there's a minor ambiguity that I should have
clarified.  References to, for example, "SGI server" should really
refer to an SGI server/client pair.  Ditto for SunOS.  I'd expect
(though I don't know for certain) that the lack of atime updates
is the fault (if "fault" is the correct term) of the client's NFS
code rather than the server's.

One thing I've not yet tried is to see what happens with respect to
atime updates when a process running on an SGI client accesses files
on a Sun server (ditto Sun client + SGI server).

Mark Bartelt                                           416/978-5619
Canadian Institute for                        mark@cita.toronto.edu
Theoretical Astrophysics                      mark@cita.utoronto.ca