Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!sunybcs!uhura.cc.rochester.edu!troi.cc.rochester.edu!leadley
From: leadley@troi.cc.rochester.edu (Scott Leadley)
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP and SunOS4.1 (not, oops, BSD)
Summary: its a bug (suprise!)
Keywords: CAP, Sun, oops
Message-ID: <8192@ur-cc.UUCP>
Date: 6 Jul 90 20:57:43 GMT
References: <4699@milton.u.washington.edu> <1025@idunno.Princeton.EDU>
Sender: news@uhura.cc.rochester.edu
Organization: University of Rochester, Rochester NY
Lines: 16

In article <1025@idunno.Princeton.EDU> sproule@idunno.Princeton.EDU (William J.  Jr. Sproule) writes:
...
>we have tried this, and had problems with nfs. when running aufs and
>mounting a local disk, aufs run fine.  when running aufs and the mount
>was a nfs disk mounted from another 4.1 machine, aufs run fine.  however,
>when mounting a disk that what nfs mounted from a sun running 4.0.3, or
>another 4.3 BSD machine (next floptical) we had problems with
>filelocking.  the lockd got very confused on the sun, and usually had
>to be killed and restarted.  ...

	Yup.  We had this problem (of lockd getting very confused) too.  Call
Sun and get the patched versions of rpc.lockd and rpc.statd for SunOS 4.0.3.
I believe based on their behavior that the SunOS 4.1 versions of rpc.lockd and
rpc.statd have fixed the problem also.
--
					Scott Leadley - leadley@cc.rochester.edu