NFS Lock Manager on 386 versions

Article View: comp.sys.sun

Article #1542

#1542

From: Todd
Date: Wed, 20 Sep 1989 14:34

12 lines
1117 bytes

The Lock Manager (LOCKD) does not work properly on 386 versions of TCP+NFS
supplied by Interactive and Wollongong.  Interactive explicity states that
the LOCKD daemon has been disabled since it does not work properly, and
Wollongong lets you find out on your own.  I realize that this may not be
your problem since you licensed the source code, but the proliferation of
NFS is being hampered by this problem.  Do you know of any fix's for this
problem, or know of other vendors who have the LOCKD feature on a 386
based NFS ?  What is the seemingly insurmountable wall on the 386 based
UNIX implementations ?  Your comments will be greatly appreciated.  

Steve Mazur
(todd)

Technical Details

Message-ID: <1620@brazos.Rice.edu>

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!wuarchive!uwm.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!wuarchive!uwm.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: todd@dtrc.dt.navy.mil (Todd)
Newsgroups: comp.sys.sun
Subject: NFS Lock Manager on 386 versions
Keywords: 386i
Message-ID: <1620@brazos.Rice.edu>
Date: 20 Sep 89 14:34:37 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 12
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 130, message 12 of 18