Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!ukc!edcastle!cs.ed.ac.uk!paul
From: paul@cs.ed.ac.uk (Paul Anderson)
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP6.0 -- incompatible lock daemons?
Message-ID: <10989@skye.cs.ed.ac.uk>
Date: 17 May 91 07:36:04 GMT
References: <14881@hacgate.UUCP>
Sender: nnews@cs.ed.ac.uk
Organization: Department of Computer Science, University of Edinburgh
Lines: 24

In article <14881@hacgate.UUCP>, lance@luna.dpl.scg.hac.com (Lance Telepnev) writes:
> 
> Is anyone out there having problems with CAP6.0 running on 4.1.1?
> I have it running on a sun3 running 4.1.1 and it seems to work just fine
> till someone tries to access a file on a mounted partition that is not local
> ........
> Does that mean that I have to upgrade all the machines to 4.1.1 before
> everything will work correctly?  Or is there some sort of work around for this?
> 
> I suspect a problem with incompatible lock daemons between operating systems.

Try "broken" rather than "incompatible". Flock had lots of problems
under SunoS until recently. I had to disable all locking in CAP to run it
sucessfully under 4.0.3. I believe that 4.1.1 contains lots of locking fixes
and things should work now, but I haven't been brave enough to put the
locking back in my version of CAP yet.

You might be able to get a patch tape from Sun, but the answer is probably an upgrade to 4.1.1.

-- 
Paul Anderson                      JANET: paul@uk.ac.ed.lfcs
LFCS, Dept. of Computer Science    UUCP:  ..!mcvax!ukc!lfcs!paul	
University of Edinburgh            ARPA:  paul%lfcs.ed.ac.uk@nsfnet-relay.ac.uk
Edinburgh EH9 3JZ, UK.             Tel:   031-650-5193