From owner-freebsd-ports@FreeBSD.ORG Sat Mar 25 00:01:14 2006 Return-Path: X-Original-To: freebsd-ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C86616A48F for ; Sat, 25 Mar 2006 00:01:14 +0000 (UTC) (envelope-from lawrance@FreeBSD.org) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CE1D43D64 for ; Sat, 25 Mar 2006 00:01:00 +0000 (GMT) (envelope-from lawrance@FreeBSD.org) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout1.pacific.net.au (Postfix) with ESMTP id 57EAF347FD1; Sat, 25 Mar 2006 11:00:59 +1100 (EST) Received: from [192.168.0.7] (ppp2D45.dyn.pacific.net.au [61.8.45.69]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id k2P00vDU024325; Sat, 25 Mar 2006 11:00:58 +1100 In-Reply-To: References: <0EF5CD301A7EA4ABAE895ACD@utd59514.utdallas.edu> <20E2B4EA-AD51-4B06-B52E-8938D5C4855B@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Sam Lawrance Date: Sat, 25 Mar 2006 11:00:55 +1100 To: Paul Schmehl X-Mailer: Apple Mail (2.746.2) Cc: freebsd-ports@FreeBSD.org Subject: Re: Startup at boot problem X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Mar 2006 00:01:14 -0000 On 25/03/2006, at 10:47 AM, Paul Schmehl wrote: > --On Saturday, March 25, 2006 10:03:59 +1100 Sam Lawrance > wrote: >>> >>> I solved the problem by using the full path in the script. >>> Originally it had "exec tclsh8.4". I patched it to have "exec /usr/ >>> local/bin/tclsh8.4", and it starts fine on boot now. Obviously >>> PATH didn't have /usr/local/bin in it at the time the script was >>> being initiated. >> >> I'm not sure you do understand what it means. Is there an rc with a >> "PROVIDE: tclsh8.4" line to match your REQUIRE? >> > Maybe I don't. I *thought* PROVIDE: used ${name}, as in the name > of the daemon or script. Is that incorrect? Yes. There's some information about it in rcorder(8). It's rcorder that produced the initial error message you showed - because it couldn't find a PROVIDE to match the REQUIRE.