Xref: utzoo comp.sys.dec:4425 comp.unix.ultrix:5208 comp.protocols.nfs:1469
Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!gatech!purdue!haven!decuac!bacchus.pa.dec.com!shodha.enet.dec.com!alan
From: alan@shodha.enet.dec.com ( Alan's Home for Wayward Notes File.)
Newsgroups: comp.sys.dec,comp.unix.ultrix,comp.protocols.nfs
Subject: Re: NFS bug in Ultrix 3.1  (on DEC3100)
Summary: Submit an SPR.
Message-ID: <1925@shodha.enet.dec.com>
Date: 6 Nov 90 05:57:17 GMT
References: <1990Nov6.022044.19498@watcgl.waterloo.edu>
Followup-To: comp.sys.dec
Organization: Digital Equipment Corp. - Colorado Springs, CO.
Lines: 29

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
> implementations under Ultrix (Ultrix-32 V3.1 (Rev. 11)).  The VAXen servers
> kept crashing while testing my client, and I wondered why - it seems that any
> time I refer to a file outside the filesystem I have mounted (either through an
> 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?

	It sounds vaguely familiar.  It is also probably fixed in
	V4.0, so you should consider installing V4.
> 
> Is there a proper DEC contact point for sending such bug reports?

	Go through your doc set and look for a half-dozen or so
	carbon paper thing.  If it says Software Performance
	Report, then you've found the right one.  If you don't
	find one can get one from your local DEC office.  If you
	have a support contract you might be submit one through
	them without ever having to touch the paper kind.

> -- 
> Marc E. Gauthier   megauthier@watcgl.waterloo.edu   University of Waterloo
> 		   129.97.128.64		    885-1211 x3469 or x4548


-- 
Alan Rollow				alan@nabeth.enet.dec.com