From owner-freebsd-current@FreeBSD.ORG Sun Jul 31 19:00:25 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DBDC16A41F for ; Sun, 31 Jul 2005 19:00:25 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E3F643D5E for ; Sun, 31 Jul 2005 19:00:24 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.4/8.13.4) with ESMTP id j6VJ0Mhf004705 for ; Sun, 31 Jul 2005 12:00:24 -0700 (PDT) (envelope-from marcel@xcllnt.net) Mime-Version: 1.0 (Apple Message framework v622) Content-Transfer-Encoding: 7bit Message-Id: <560747f4f3d58887485e1a2c0c25ac26@xcllnt.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: current@freebsd.org From: Marcel Moolenaar Date: Sun, 31 Jul 2005 12:00:20 -0700 X-Mailer: Apple Mail (2.622) Cc: Subject: 6.0-BETA1: rpc.lockd broken for NFS server only configuration X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jul 2005 19:00:25 -0000 Gang, I upgraded to 6.0-BETA1 for my NFS server yesterday and rpc.lockd stopped working as an immediate result of that. The error being logged is: rpc.lockd: nfslock: No such file or directory Apparently the nfslock pseudo-device is only compiled into the kernel when device nfsclient is present. This would indicate that I don't need rpc.lockd running on the server. However, NFS clients hang when they try to lock files across NFS: bigsur% vi pmap.c *hang* */me typing ^T after a couple of minutes* load: 0.00 cmd: vi 457 [lockd] 0.01u 0.01s 0% 2976k This tells me that NFS locking does not work if rpc.lockd is not running on the server. I could of course add nfsclient to my kernel configuration file, but that annihilates the effort to split the server functionality from the client functionality, so that's no solution. In short: NFS locking is broken again -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net