explicit use of /etc/rc.d vs service

[Elias Chrysocheris]

>Sounds like a very good idea. I don't know how many times I have had
>problems with bad paths leaking into cron etc meaning it fails on reboot
>since something depended on the trained environment. (Service solves that.)

Yes, but there are sometimes that service does not act as it should be. For 
example, in my FreeBSD 9.1 (happened also in 8.x) service apache22 onerestart, 
restarts apache22 but there something is missing... I do not have access to my 
mercurial web interface. It returns an error. But when I 
/usr/local/etc/rc.d/apache22 onerestart evrything works fine...

Regards
Elias