[62] in 6.033-lab
final things.
daemon@ATHENA.MIT.EDU (ben@MIT.EDU)
Mon May 12 12:27:27 1997
From: ben@MIT.EDU
Date: Mon, 12 May 97 12:27:07 -0400
To: Kevin 'Frostbyte' McCormick <fbyte@sub-zero.mit.edu>
Cc: 6.033-lab@MIT.EDU
In-Reply-To: <Pine.LNX.3.93.970512050921.4043A-100000@sub-zero.mit.edu>
Reply-To: ben@MIT.EDU
Kevin,
I had a "caching" problem of some kind, too, which was related to the
last modification time of files. The original sfscd sets the
modification time of everything to be the current time, which most
definitely will flush the cache. If you set your modification time to
be constant (which is a typical hack to not deal with time), then you
may run into these cache problems.
This may be a shot in the dark, but at the same time I thought it
might be useful if others have this problem.
Note also that my constant loop on reads was caused by the fact that I
always returned the current time as the modification time, which made
the NFS client think that my file was being constantly updated, and
thus that it was never getting the latest version.... (see where this
is going?)....
-Ben
