From owner-freebsd-questions@FreeBSD.ORG Fri Oct 12 22:41:03 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D5C716A417 for ; Fri, 12 Oct 2007 22:41:03 +0000 (UTC) (envelope-from nollan@phreaker.net) Received: from av9-2-sn3.vrr.skanova.net (av9-2-sn3.vrr.skanova.net [81.228.9.186]) by mx1.freebsd.org (Postfix) with ESMTP id 0E71113C448 for ; Fri, 12 Oct 2007 22:41:02 +0000 (UTC) (envelope-from nollan@phreaker.net) Received: by av9-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 3C5AA3849B; Sat, 13 Oct 2007 00:41:01 +0200 (CEST) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av9-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 210D738261 for ; Sat, 13 Oct 2007 00:41:01 +0200 (CEST) Received: from [10.10.10.2] (81-237-246-236-no120.tbcn.telia.com [81.237.246.236]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 0A5B137E43 for ; Sat, 13 Oct 2007 00:41:00 +0200 (CEST) Message-ID: <470FF81B.8010609@phreaker.net> Date: Sat, 13 Oct 2007 00:41:31 +0200 From: "mr. phreak" User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: rpc_lockd and syslogd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2007 22:41:03 -0000 I have a chicken-egg problem. On my diskless setup the syslogd gives me this error during boot: syslogd: cannot open pid file: operation not supported And I tracked the issue to flock() and enabled rpc_lockd. Still it gives me the same error - because rpc_lockd starts AFTER syslogd does. I've tried fiddling around with REQUIRES and PROVIDES in the rc.d files but I cannot make it work... It gives me the error anyway. (or other errors due to rc.d-hacking)... is there any way to solve this? I'd appreciate some help! when running syslogd when logged in it doesn't give me the error so I guess rpc_lockd *really* is the sollution. regards J