Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pcserver2!genesis!kdenning
From: kdenning@genesis.Naitc.Com (Karl Denninger)
Newsgroups: comp.sys.mips
Subject: Re: rpc.lockd
Summary: It's STILL not fixed
Message-ID: <1991May3.223342.15002@pcserver2.naitc.com>
Date: 3 May 91 22:33:42 GMT
References: <2383@cluster.cs.su.oz.au> <3019@spim.mips.COM>
Sender: news@pcserver2.naitc.com (Usenet admin)
Organization: AC Nielsen Co., Bannockburn IL
Lines: 30
Nntp-Posting-Host: genesis.naitc.com

In article <3019@spim.mips.COM> trevc@mips.com writes:
>In article <2383@cluster.cs.su.oz.au>, jaa@cluster.cs.su.oz.au (James Ashton) writes:
>|> There seem to be a large number of bugs with this programme.  We have
>|> found the following problems using fcntl to gain advisory exclusive
>|> locks across multiple hosts.
>|> 
>
>Our engineering group has spent a large amount of time fixing numerous
>problems in the Sun rpc.lockd code. The fruits of their labor are available
>in the form of an updated rpc.lockd for RISC/os 4.52.
>
>If you have software maintenance, you can contact the MIPS Customer Response
>Center on 1-800-443-MIPS to request a copy.

I have the MIPS "fixed" rpc.lockd.

They have a HUGE memory leak in them which makes the process grow until it
consumes all available physical memory.

Last time I killed it, the process had more than 4,000 pages checked out!

Try again please.

--
Karl Denninger - AC Nielsen, Bannockburn IL (708) 317-3285
kdenning@nis.naitc.com

"The most dangerous command on any computer is the carriage return."
Disclaimer:  The opinions here are solely mine and may or may not reflect
  	     those of the company.