Date: Mon, 28 Mar 2016 11:55:10 -0700 From: Sergei G <sergeig.public@gmail.com> To: "Kevin P. Neal" <kpn@neutralgood.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: how to troubleshoot services startup on reboot Message-ID: <CAFLLzCNxjOL=C4EDLzdU7ax0uFC4Y-B_kWA9u59F0RfC1vrfrg@mail.gmail.com> In-Reply-To: <20160328180531.GA76011@neutralgood.org> References: <CAFLLzCP2rjx%2BfL6upNC8E=f-0JVRvaxJ9VWYftaK970WOQLrcA@mail.gmail.com> <20160328180531.GA76011@neutralgood.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I know about the service -e command. However, that's of little help when it comes to service startup order. I've had this problem in the past with FreeBSD Hyper-V guest, because it was taking too long to obtain IP from DHCP. I even had to set a setting to make it wait to obtain IP prior to proceeding with the rest of boot. On Mon, Mar 28, 2016 at 11:05 AM, Kevin P. Neal <kpn@neutralgood.org> wrote: > On Mon, Mar 28, 2016 at 10:57:00AM -0700, Sergei G wrote: > > I have service startup failure probably due to DNS resolution. I think > > that local unbind is not available during some services startup. For > > example, nginx reports failure to resolve network names and fails to > start. > > > > However, there is little I can obtain about service startup order from > > logs, because there is no entry like "starting local unbind" in > > /var/log/messages. > > Use the 'service' command. Try 'service -e', but I'm not 100% sure if it > will print all enabled services. But 'service -r' will show you everything > including the stuff that is turned off. > -- > Kevin P. Neal http://www.pobox.com/~kpn/ > > "It sounded pretty good, but it's hard to tell how it will work out > in practice." -- Dennis Ritchie, ~1977, "Summary of a DEC 32-bit machine" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFLLzCNxjOL=C4EDLzdU7ax0uFC4Y-B_kWA9u59F0RfC1vrfrg>