Alex Zbyslaw wrote:
Chad Leigh -- Shire.Net LLC wrote:
On Jun 14, 2005, at 1:39 PM, JM wrote:
Kirk Strauser wrote:
On Tuesday 14 June 2005 12:07, JM wrote:
i've written an rcNG script but i'm having some issues.
Step one: set rc_debug="YES" in /etc/rc.conf to see what's
actually happening when you attempt to run your script. That
seems to uncover about 95% of the problems I've had.
turned on the option rc_debug="YES" and ran 'dmesg -a'... the
script doesn't even show up in the list anywhere. are we not
supposed to be able to write custom rcNG scripts? is there
something i'm overlooking where i need to register httpd_start in
the rc stuff? here's my newbie impression of how rc works:
- rc i run by init
- rc runs rcorder on all script directories.
- rc reads rc.conf and runs all scripts found by rcorder
rcorder recognizes the script i wrote without any errors... yet
when i boot the system, there is no "checkyesno" for httpd_start.
there's nothing that references the script at all... WHY? >.<
why did FreeBSD have to adopt this standard anyhow? it seems
unnecessarily complicated to write custom scripts now.
Where does your script live? You can use rcNG style scripts in /usr/
local/etc but they must end in .sh and are done in lexographic
order without the rcorder and stuff (unless you write your own
ueber- script to do it)
I battled this for a long while before I figured out the /usr/local/
etc does not get full rcNG support
I did the same, wondering why scripts weren't even running etc, until
I read what the manual page actually said rather than what I wanted it
to say :-)
Does anyone know why this is? Will /usr/local/etc et al. be getting
proper rcNG support? Otherwise port and locally installed software
are effectively second class citizens and don't get to benefit
especially from the dependency stuff. Currently I'm stuffing local
(not port) startups in /etc/rc.d, which I don't like doing (and
mergemaster complains about them being obsolete -- I guess trying to
spot stuff left over from 4.X). It would be great to know what the
plans are.
--Alex
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
yea that's the whole reason i was attempting to get this done right. i
hate doing work that will be deprecated or fondled or otherwise abused
in later releases.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"