On Tue, 23 Nov 1999, Ronald G. Minnich wrote:
:On Mon, 22 Nov 1999, David E. Cross wrote:
:> I've noticed about 99% of the panics on our machines are the result of NFS,
:> more often than not it is the result of a backing store file being blown
:> away underneath the client. ie. person editing
On Mon, 22 Nov 1999, David E. Cross wrote:
> I've noticed about 99% of the panics on our machines are the result of NFS,
> more often than not it is the result of a backing store file being blown
> away underneath the client. ie. person editing a file on one machine,
> compiling and running on
> That's really up to the server lockd/nfsd implementation, but considering
> that more likely than not the server's lockd will have an open reference
> to the file until the lock is gone the answer is probably yes.
Hmm... I wold think even without having the file "open" a lock would be
enough. S
On Mon, 22 Nov 1999, David E. Cross wrote:
> I've noticed about 99% of the panics on our machines are the result of NFS,
> more often than not it is the result of a backing store file being blown
> away underneath the client. ie. person editing a file on one machine,
> compiling and running o
I've noticed about 99% of the panics on our machines are the result of NFS,
more often than not it is the result of a backing store file being blown
away underneath the client. ie. person editing a file on one machine,
compiling and running on a second, then removing the binary on the first
ma
5 matches
Mail list logo
