Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!bbs!karl
From: karl@naitc.naitc.com (Karl Denninger)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: PD NFS
Summary: Oh, that's ok.  Sun rpc.lockd is STILL BROKEN folks
Message-ID: <1990Oct19.154034.16773@naitc.naitc.com>
Date: 19 Oct 90 15:40:34 GMT
References: <9010171443.AA00942@tmc.edu>
Reply-To: karl@bbs.naitc.com (Karl Denninger)
Organization: A.C. Nielsen Co.
Lines: 29

In article <9010171443.AA00942@tmc.edu> sob@tmc.edu (Stan Barber) writes:
>Yes, there have been versions shipped that didn't work. That is not really
>the point. Anyone running modern version of SunOS (4.0.3 or 4.1) should be
>able to run a working lock daemon.
>
>The real point is that some vendors don't support any form of locking that
>notifies other potential users of the file that it is locked. This is BAD.
>
>Now that this locking protocol has been published by X/Open, it should be
>much easier to get it right. I hope that various vendors will try.
>
>STAN

Of course, Sun is still shipping distribution 4.1 tapes with a broken
rpc.lockd, and they don't tell you about the bug until you scream at them
and/or buy a service contract.  Considering that they know darn well that
the stock version is broken (it drives the kernel out of resources and blows
up) I consider this "omission" to be a real problem.

Their >new< and >improved< rpc.lockd still isn't solid - it has a habit of
dying (ie: exiting) which REALLY screws things up -- as in locks up every
process which has a file open on the machine which exited.

--
Karl Denninger	AC Nielsen
kdenning@ksun.naitc.com
(708) 317-3285
Disclaimer:  Contents represent opinions of the author; I do not speak for
	     AC Nielsen on Usenet.