Date: Sat, 25 Mar 2006 11:00:55 +1100 From: Sam Lawrance <lawrance@FreeBSD.org> To: Paul Schmehl <pauls@utdallas.edu> Cc: freebsd-ports@FreeBSD.org Subject: Re: Startup at boot problem Message-ID: <AA6B5939-D92A-4F42-9999-967ACAE0CFEA@FreeBSD.org> In-Reply-To: <A198D45BDDF6A91C6112FAEE@utd59514.utdallas.edu> References: <0EF5CD301A7EA4ABAE895ACD@utd59514.utdallas.edu> <D25CA5D6-C919-4248-B1D2-8686ED77166D@FreeBSD.org> <B6CE362B7099434BC86EABD1@utd59514.utdallas.edu> <20E2B4EA-AD51-4B06-B52E-8938D5C4855B@FreeBSD.org> <A198D45BDDF6A91C6112FAEE@utd59514.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25/03/2006, at 10:47 AM, Paul Schmehl wrote:
> --On Saturday, March 25, 2006 10:03:59 +1100 Sam Lawrance
> <lawrance@FreeBSD.org> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AA6B5939-D92A-4F42-9999-967ACAE0CFEA>