From owner-freebsd-stable@FreeBSD.ORG Sun Jan 9 18:44:05 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E779C106564A for ; Sun, 9 Jan 2011 18:44:05 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id A6F4F8FC18 for ; Sun, 9 Jan 2011 18:44:05 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAEGRKU2DaFvO/2dsb2JhbACEA6EuriKMS4EhgVaBYXQEhGeGIw X-IronPort-AV: E=Sophos;i="4.60,296,1291611600"; d="scan'208";a="106434706" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 09 Jan 2011 13:44:04 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id ABB65B3F24; Sun, 9 Jan 2011 13:44:04 -0500 (EST) Date: Sun, 9 Jan 2011 13:44:04 -0500 (EST) From: Rick Macklem To: Daniel Feenberg Message-ID: <535791711.18255.1294598644612.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE8 (Win)/6.0.10_GA_2692) Cc: freebsd-stable@freebsd.org Subject: Re: Specifying root mount options on diskless boot. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2011 18:44:06 -0000 > Daniel Braniss writes... > > > I have it pxebooting nicely and running with an NFS root > > but it then reports locking problems: devd, syslogd, moused (and > > maybe > > others) lock their PID file to protect against multiple instances. > > Unfortunately, these daemons all start before statd/lockd and so the > > locking fails and reports "operation not supported". > > Are you mounting /var via nfs? You can use the "nolockd" mount option to make locking happen locally in the client. (Only a problem if the file(s) being locked are concurrently shared with other clients.) I don't know if this would fix your diskless problem. rick