Date: Thu, 24 Jan 2013 18:21:49 +0100 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Elias Chrysocheris <elias_chr@otenet.gr> Cc: freebsd-doc@freebsd.org Subject: Re: explicit use of /etc/rc.d vs service Message-ID: <20130124172148.GA14943@saturn> In-Reply-To: <201301241452.26474.elias_chr@otenet.gr> References: <CAF6rxgnJPFevO7W%2BypBZdcL7deB%2B_cQHF0AEcVaWWv8FFhcNcQ@mail.gmail.com> <CAC8HS2Ewh391gbCQb2QFm8k3-uUUKp=5bibrmy4RAnNj93V1Ew@mail.gmail.com> <201301241452.26474.elias_chr@otenet.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-01-24 14:52, Elias Chrysocheris <elias_chr@otenet.gr> wrote: > >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... Is there any case this could be a WSGI bug? I know that Mercurial's web interface has WSGI capabilities, so maybe something is 'stuck' after onestart and it's not related to 'service' but to what happens when one runs any sort of WSGI service under apache. Not that this is not a real problem, though. Just that we should try to solve the underlying issue, if any, and make it easier to use service XXX commands. - Giorgos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130124172148.GA14943>