From owner-freebsd-questions  Tue Mar 31 15:23:07 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA23354
          for freebsd-questions-outgoing; Tue, 31 Mar 1998 15:23:07 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from paris.dppl.com (qmailr@paris.dppl.com [205.230.74.150])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA22840
          for <questions@FreeBSD.ORG>; Tue, 31 Mar 1998 15:21:28 -0800 (PST)
          (envelope-from yds@ingress.com)
Received: (qmail 11168 invoked from network); 31 Mar 1998 23:21:05 -0000
Received: from ichiban.ingress.com (HELO ichiban) (205.230.64.31)
  by paris.dppl.com with SMTP; 31 Mar 1998 23:21:05 -0000
Message-ID: <00fd01bd5cfb$aceaaf10$1f40e6cd@ichiban.ingress.com>
From: "Yarema" <yds@ingress.com>
To: <questions@FreeBSD.ORG>
Subject: rpc.lockd(8)
Date: Tue, 31 Mar 1998 18:21:03 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I noticed the rpc.lockd(8) man page is dated September 24, 1995 and the BUGS
section claims:

BUGS
     The current implementation provides only the server side of the
protocol
     (ie. clients running other OS types can establish locks on a FreeBSD
     fileserver, but there is currently no means for a FreeBSD client to es­
     tablish locks).

Is that still the case that FreeBSD clients cannot establish locks?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message