From owner-freebsd-questions Tue Dec 1 08:23:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13754 for freebsd-questions-outgoing; Tue, 1 Dec 1998 08:23:30 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ns.novator.com ([199.45.114.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13742 for ; Tue, 1 Dec 1998 08:23:24 -0800 (PST) (envelope-from vmg@ns.novator.com) Received: (from vmg@localhost) by ns.novator.com (8.8.8/8.8.8) id LAA06127 for freebsd-questions@freebsd.org; Tue, 1 Dec 1998 11:18:57 -0500 (EST) Message-Id: <199812011618.LAA06127@ns.novator.com> Subject: lockd To: freebsd-questions@FreeBSD.ORG Date: Tue, 1 Dec 1998 11:18:57 -0500 (EST) From: "Victor Granic" X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, In /etc/rc.conf the comment after [en,dis]abling lockd says it's broken. I had been trying to use it before I noticed the comment and in fact, it really is broken. I cannot exclusively lock a file on an NFS mounted partition from my FreeBSD machines. Is this problem fixed in 2.2.8 or 3.0? Is there an alternative to using the default lockd? Could I compile/install another one that isn't broken? Thank you, Victor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message