Xref: utzoo comp.sys.dec:4462 comp.unix.ultrix:5276 comp.protocols.nfs:1495
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!mcdchg!tellab5!wheaton!stefan
From: stefan@wheaton.UUCP (Stefan Brandle )
Newsgroups: comp.sys.dec,comp.unix.ultrix,comp.protocols.nfs
Subject: Re: NFS bug in Ultrix 3.1  (on DEC3100)
Message-ID: <2374@wheaton.UUCP>
Date: 8 Nov 90 22:22:03 GMT
References: <1990Nov6.022044.19498@watcgl.waterloo.edu>
Reply-To: stefan@wheaton.UUCP (Stefan Brandle )
Organization: Wheaton College, IL
Lines: 20

In article <1990Nov6.022044.19498@watcgl.waterloo.edu> megauter@watcgl.waterloo.edu (Marc E. Gauthier) writes:
>In developing an NFS client implementation, I discovered a bug in NFS server
...
>unmounted mount point, or by giving absolute path names), the VAX panics and
>reboots.  Although what I was doing was `improper' client behaviour since I
>was giving pathnames for the server to parse, it still shouldn't crash the
>server...  Anybody come upon this?

We are using a GatorBox that allows Macintoshes to access NFS servers and see
the files there as AppleShare volumes.  It's a very nice idea, except that when
doing big multi-file copying we can crash any of our VAXen almost on demand.
I had never gotten anywhere trying to determing what happened; maybe it's
related.  I agree that a client should not be able to crash the server.

-Stefan Brandle
-- 
---------------------------------------------- MA Bell: (708) 260-4110 ---------
Stefan Brandle                  UUCP: ...!{obdient,uunet!tellab5}!wheaton!stefan
Wheaton College			or	stefan@wheaton.UUCP
Wheaton, IL 60187 		"But I never claimed to be sane!"