From owner-freebsd-questions@FreeBSD.ORG Sat Oct 13 12:36:56 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 E747616A420 for ; Sat, 13 Oct 2007 12:36:56 +0000 (UTC) (envelope-from nollan@phreaker.net) Received: from av8-1-sn3.vrr.skanova.net (av8-1-sn3.vrr.skanova.net [81.228.9.183]) by mx1.freebsd.org (Postfix) with ESMTP id A155013C46B for ; Sat, 13 Oct 2007 12:36:56 +0000 (UTC) (envelope-from nollan@phreaker.net) Received: by av8-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 2C31A38421; Sat, 13 Oct 2007 14:36:55 +0200 (CEST) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av8-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 11F2E381A5; Sat, 13 Oct 2007 14:36:55 +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 B054E37E48; Sat, 13 Oct 2007 14:36:54 +0200 (CEST) Message-ID: <4710BC0A.4090609@phreaker.net> Date: Sat, 13 Oct 2007 14:37:30 +0200 From: "mr. phreak" User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: fbsd.questions@rachie.is-a-geek.net, freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: 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: Sat, 13 Oct 2007 12:36:57 -0000 Message: 16 Date: Sat, 13 Oct 2007 01:06:26 +0200 From: Mel Subject: Re: rpc_lockd and syslogd To: freebsd-questions@freebsd.org Message-ID: <200710130106.26923.fbsd.questions@rachie.is-a-geek.net> Content-Type: text/plain; charset="iso-8859-1" On Saturday 13 October 2007 00:41:31 mr. phreak wrote: > > 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. > Or the solution is specifying a pid file on a memory disk? I can't think of any issues with /var/run being /dev/md*, but there might some. In any case, syslogd_flags="-s -P /tmp/syslogd.pid" should work as well. The issue I see with that is that /etc/rc.d/syslogd doesn't expose it's pidfile for outside configuration. -- Mel Since I don't have memorydisks, only nfs-mounts (/tmp and /var) the problem still remains. It's really a chicken-egg problem and I can't find any new point of view to tackle the issue. The best would be if someone successfully have altered the rc.d-scrips for a correct rcorder and would like to share it - i.e rpc_lockd BEFORE syslogd. J