Date: Wed, 23 Sep 2015 15:32:03 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Eugene M. Zheganin" <emz@norma.perm.ru> Cc: stable@freebsd.org Subject: Re: when the sshd hits the fan Message-ID: <86wpvhjm7g.fsf@nine.des.no> In-Reply-To: <56026686.8030308@norma.perm.ru> (Eugene M. Zheganin's message of "Wed, 23 Sep 2015 13:44:54 %2B0500") References: <56026686.8030308@norma.perm.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
"Eugene M. Zheganin" <emz@norma.perm.ru> writes: > I'm trying to understand why the sshd still starts after local daemons, > out-of-the-box, and what it takes to make this extremely vital service > to start before non-system (local) ones. I bet I'm not the first one to > ask, so why isn't this already done ? Seems quite easy for me. "non-system (local)" services can also be extremely vital: quagga, for instance. In practice, it is probably fine to move sshd before LOGIN. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86wpvhjm7g.fsf>