Return to BSD News archive
Xref: sserve comp.unix.bsd:4425 comp.sources.wanted:13343 comp.unix.sysv386:23229 Path: sserve!manuel!munnari.oz.au!uunet!cs.utexas.edu!rutgers!igor.rutgers.edu!athos.rutgers.edu!hedrick From: hedrick@athos.rutgers.edu (Charles Hedrick) Newsgroups: comp.unix.bsd,comp.sources.wanted,comp.unix.sysv386 Subject: Re: lockd sources Message-ID: <Sep.1.23.11.03.1992.23758@athos.rutgers.edu> Date: 2 Sep 92 03:11:04 GMT References: <vsjn8bc.damon@netcom.com> <jrh.715384152@mustang> Followup-To: comp.unix.bsd Organization: Rutgers Univ., New Brunswick, N.J. Lines: 25 jrh@mustang.dell.com (Randy Howard) writes: >damon@netcom.com (Damon Skaggs) writes: >>I have having terrible problems slowness problems in lockd. Is there >>any PD implementation of lockd available to see if I can figure out >>what is going on? BTW, does BSDI have lockd? >This is a well-known problem with the USL lockd. It is very slow, and >in a lot of cases, broken. I think all SVR4 vendors will have this >problem unless someone has managed to fix it. We have a lot of experience with lockd on SunOS. (I assume SVr4 got it from there.) There have been many releases. It's been getting better slowly, but I still do not entirely trust it. Furthermore, I would suspect that your SVr4 is not likely to be up to date with the latest Sun fixes. Thus I would regard lockd as of dubious reliability. Unfortunately this is one of the few network utilities I know of where there is no free equivalent. (At least I've never heard of it, and I think I would have.) Generally it's possible to do locking by creating a separate lock file. We urge our staff to do this rather than depend upon lockd. Of course if you have to lock regions of files, that's not an answer. Fortunately we don't have any applications like that.