Sendmail for one can hang for stupidly long times waiting in dead resolvers before allowing the system to continue booting. 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. On Wednesday, September 23, 2015, Glenn English <ghe at slsware.net> wrote:> Mildly OT from a profound BSD noob: > > Why is it necessary to have SSH working before the system has finished > booting? That 'Welcome' menu times out, so I can't think of a reason, or > find one from Goggle, for needing console access after a power failure > reboot. What am I unaware of? > > -- > Glenn English > > > > _______________________________________________ > freebsd-stable at freebsd.org <javascript:;> mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org > <javascript:;>" >-- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler
On Sep 23, 2015, at 10:00 AM, Michael Loftis <mloftis at wgops.com> wrote:> Sendmail for one can hang for stupidly long times waiting in dead resolvers before allowing the system to continue booting.So replace it with Postfix? I've been using it (on Debian Linux) for decades without any problems. AFAIK, it doesn't do anything pathological like that. It just reads its config and starts waiting for email.> 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? 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. -- Glenn English