Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!yoyo.aarnet.edu.au!sirius.ucs.adelaide.edu.au!augean.ua.OZ.AU!flinders!lennon!clapton!cwilson
From: cwilson@clapton.austek.oz (Chris Wilson)
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP6.0 -- incompatible lock daemons?
Message-ID: <107@clapton.austek.oz>
Date: 15 May 91 08:20:00 GMT
References: <14881@hacgate.UUCP>
Reply-To: cwilson@austek.oz.au (Chris Wilson)
Organization: Austek Microsystems Pty. Ltd., Adelaide, South Australia
Lines: 23

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
>to the machine AND THAT machine is NOT running 4.1.1, rather 4.0.3.
>The mac hangs forever forcing me to reboot the mac.  The macintosh typically
>hangs after about the same amount of time while trying to copy/access either
>a large file or a small one.
>
Probably, the server machine doesn't do the correct sort of locking
using lockd. The answer is to comment out the following line from m4.setup

# lockf - "afp: byte range locking using unistd.h"
define([X_LOCKF],1)

I had a similar problem where the NFS server was a machine running an
oldish version of Ultrix and doing that fixed the problem. You can
then run gen.makes, recompile and see if it works.

Chris
ACSnet:	cwilson@austek.oz	Internet:  cwilson@austek.oz.au