From owner-freebsd-current Mon Apr 23 8:50:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from infres.enst.fr (infres-192.enst.fr [137.194.192.1]) by hub.freebsd.org (Postfix) with ESMTP id 1789D37B424 for ; Mon, 23 Apr 2001 08:50:06 -0700 (PDT) (envelope-from quinot@inf.enst.fr) Received: by infres.enst.fr (Postfix, from userid 11117) id 2AC15189C; Mon, 23 Apr 2001 17:50:05 +0200 (MET DST) Date: Mon, 23 Apr 2001 17:50:05 +0200 From: Thomas Quinot To: current@freebsd.org Subject: lockd problems Message-ID: <20010423175004.A24030@infres.enst.fr> Reply-To: Thomas Quinot Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1us Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since client side locking was implemented, I am having much trouble reading mail on an NFS-mounted mail spool. The NFS server is a Solaris 2.6 U250, and I am reading mail using mutt. When lockd is not running, mutt gets EOPNOTSUPP when trying to flock(). When lockd is running, it occasionnally gets EPERM, but not in a deterministic fashion. It also tends to leave the mailbox locked on the server even after quitting. Running lockd with debugging enabled did not show anything that looks like an abnormal condition. Anything I can do to resolve the problem? Or to help finding out what is happening? :) Thomas. -- Thomas Quinot ** Département Informatique & Réseaux ** quinot@inf.enst.fr ENST // 46 rue Barrault // 75634 PARIS CEDEX 13 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message