From owner-freebsd-current@FreeBSD.ORG Sun Jun 8 08:51:47 2003 Return-Path: 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 E5BCC37B401; Sun, 8 Jun 2003 08:51:47 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEE9E43FBF; Sun, 8 Jun 2003 08:51:46 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h58FoQOn087669; Sun, 8 Jun 2003 11:50:26 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h58FoQAm087666; Sun, 8 Jun 2003 11:50:26 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 8 Jun 2003 11:50:26 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: David Yeske In-Reply-To: <20030608050138.82947.qmail@web13506.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: net@freebsd.org Subject: Re: sendmail starts before rpc.statd and rpc.lockd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 08 Jun 2003 15:51:48 -0000 On Sat, 7 Jun 2003, David Yeske wrote: > Jun 8 00:52:33 photon sendmail[293]: h584pRfm000293: SYSERR(root): cannot > flock(./tfh584pRfm000293, fd=5, type=6, omode=40001, euid=25^C. > NFS access cache time=2 > Starting statd. > Starting lockd. > > It looks like sendmail starts before rpc.lockd and rpc.statd? This will > cause diskless clients to hang? This is a nfs server and diskless > client running 5.1-RELEASE. I'm running rpc.lockd and rpc.statd on the > server and the client. Should rpc.lockd and rpc.statd be started before > sendmail starts? Hmm. It shouldn't cause diskless clients to hang, or at least, doesn't for me. The cause of the error message, however, is exactly as you surmise -- befpre rpc.lockd, calls to flock() on the NFS file system will return an error. Is the hang you're seeing immediately after the "Starting lockd"? If you hit Ctrl-T, does it tell you anything useful? Note that unless you're running 5.x pretty close to the release, pressing Ctrl-T while a process is attempting to grab an NFS-backed file lock will result in a slipped lock and many nasty failure modes. I disabled signal delivery to processes while sleeping on an NFS lock as a workaround until out rpc.lockd addresses the "process aborts the lock request" race, which isn't handled right now. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories