Date: Wed, 23 Sep 2015 12:34:39 -0600 From: Glenn English <ghe@slsware.net> To: "stable@freebsd.org" <stable@freebsd.org> Subject: Re: when the sshd hits the fan Message-ID: <50FC7B1F-1009-449C-9215-E3EBFD0CA7F5@slsware.net> In-Reply-To: <CAHDg04thtOcSi4odnLZ7F3T9WiqyKO3gPcNbMpyAUqVg1owpcw@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 23, 2015, at 10:00 AM, Michael Loftis <mloftis@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. --=20 Glenn English
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50FC7B1F-1009-449C-9215-E3EBFD0CA7F5>