Date: Thu, 24 Jan 2013 14:52:26 +0200 From: Elias Chrysocheris <elias_chr@otenet.gr> To: freebsd-doc@freebsd.org Subject: Re: explicit use of /etc/rc.d vs service Message-ID: <201301241452.26474.elias_chr@otenet.gr> In-Reply-To: <CAC8HS2Ewh391gbCQb2QFm8k3-uUUKp=5bibrmy4RAnNj93V1Ew@mail.gmail.com> References: <CAF6rxgnJPFevO7W%2BypBZdcL7deB%2B_cQHF0AEcVaWWv8FFhcNcQ@mail.gmail.com> <CAC8HS2Ewh391gbCQb2QFm8k3-uUUKp=5bibrmy4RAnNj93V1Ew@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
>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 Eliashome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301241452.26474.elias_chr>