Date: Fri, 24 Mar 2006 16:01:50 -0800 (PST) From: "Freddie Cash" <fcash@ocis.net> To: "Paul Schmehl" <pauls@utdallas.edu> Cc: ports@freebsd.org Subject: Re: Startup at boot problem Message-ID: <44774.192.168.0.10.1143244910.squirrel@webmail.sd73.bc.ca> 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 Fri, March 24, 2006 3:47 pm, 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?
rcorder parses the rc scripts under /etc/rc.d and /usr/local/etc/rc.d.
It checks the PROVIDE: lines to make a list of all the services these
scripts provide. Then it checks the REQUIRE: lines and orders all the
scripts accordingly.
Which means, the only values you can use in REQUIRE: lines are those
that are already listed in a PROVIDE: line somewhere.
I'm willing to bet there are no scripts on your (or any) system that
have "PROVIDE: tclsh8.4" in them.
IOW, if there's no script that PROVIDEs a service, then no other
script can REQUIRE it.
----
Freddie Cash
fcash@ocis.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44774.192.168.0.10.1143244910.squirrel>