Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!haven!udel!princeton!sproule
From: sproule@idunno.Princeton.EDU (William J.  Jr. Sproule)
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP and SunOS4.1 (not, oops, BSD)
Keywords: CAP,Sun, oops
Message-ID: <1025@idunno.Princeton.EDU>
Date: 3 Jul 90 20:25:06 GMT
References: <4699@milton.u.washington.edu>
Reply-To: sproule@idunno.Princeton.EDU (William J.  Jr. Sproule)
Followup-To: comp.protocols.appletalk
Organization: Princeton University
Lines: 26

In article <4699@milton.u.washington.edu> matter@milton.u.washington.edu (Matthew Trunnell) writes:
>
>			Sorry.
>
>		sed -e s/BSD/SunOS/g
>
>The question remains, though.  Has anyone had any problems with CAP under
>SunOS 4.1?
>
>Thanks.
>
>matter
>
>(matter@ocean.washington.edu)

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.  running trace revealed that aufs was
spending all it's time in the lock.  i did not try running without
locking, but that's next. 

-b