Date: Wed, 23 Sep 2015 15:13:26 -0400 From: Lowell Gilbert <freebsd-stable-local@be-well.ilk.org> To: Glenn English <ghe@slsware.net> Cc: "stable\@freebsd.org" <stable@freebsd.org> Subject: Re: when the sshd hits the fan Message-ID: <447fnhkkyx.fsf@lowell-desk.lan> In-Reply-To: <50FC7B1F-1009-449C-9215-E3EBFD0CA7F5@slsware.net> (Glenn English's message of "Wed, 23 Sep 2015 12:34:39 -0600") References: <56026686.8030308@norma.perm.ru> <86wpvhjm7g.fsf@nine.des.no> <5602C0C2.5010102@norma.perm.ru> <EA745BDC-F5F1-4C8F-9B43-E0FE86B0AEA8@slsware.net> <CAHDg04thtOcSi4odnLZ7F3T9WiqyKO3gPcNbMpyAUqVg1owpcw@mail.gmail.com> <50FC7B1F-1009-449C-9215-E3EBFD0CA7F5@slsware.net>
index | next in thread | previous in thread | raw e-mail
Glenn English <ghe@slsware.net> writes: > On Sep 23, 2015, at 10:00 AM, Michael Loftis <mloftis@wgops.com> wrote: > >> That's the most common thing, RC scripts hanging waiting on external >> resources while you're locked out simply because sshd starts >> ridiculously late. Very common problem. > > If properly configed, shouldn't things come up in order, with their > dependencies already running? Or is specifying boot order not possible > on FBSD? Yes; that's done with rcorder(8). The startup order isn't completely defined, just the dependencies that require being started before (or, occasionally, after) some other service. > I can certainly understand the possible need for SSH, just for incase, > but I'd think things could be set to do stuff in the proper > order. Except for cyclic dependencies, of course -- a significant bug > for the maintainers. The discussion here is whether the "proper order" should be changed from the current default. As for cycles in the graph, rcorder already detects that.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?447fnhkkyx.fsf>