From owner-freebsd-stable Thu Mar 12 15:52:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29844 for freebsd-stable-outgoing; Thu, 12 Mar 1998 15:52:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29824 for ; Thu, 12 Mar 1998 15:52:24 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id UAA04846; Thu, 12 Mar 1998 20:51:58 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199803122351.UAA04846@gaia.coppe.ufrj.br> Subject: Re: rpc.lockd on 2.2.5-STABLE In-Reply-To: <199803111715.MAA29952@rstcorp.com> from "Viren R. Shah" at "Mar 11, 98 12:15:24 pm" To: viren@rstcorp.com Date: Thu, 12 Mar 1998 20:51:58 -0300 (EST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk #define quoting(Viren R. Shah) // Does anyone know what the state of rpc.lockd is in 2.2.5-STABLE? It answers OK for every client requesting a lock, without testing or getting a real lock. It's just a fake for clients that refuse to work without NFS locks. // On a slightly different note: How bad is NFS-mounting mailboxes from a // FreeBSD NFS-server? TM If your mail system needs lock, it a REAL MESS. It'll appear to work perfectly, until you lose your first mailbox. Now I use NFS for everything but mail. It safer to rsh to the mail server, and read mail from there. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message