From owner-freebsd-stable@freebsd.org  Wed Sep 23 16:56:42 2015
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E465A070EA
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 23 Sep 2015 16:56:42 +0000 (UTC)
 (envelope-from emz@norma.perm.ru)
Received: from elf.hq.norma.perm.ru (unknown [IPv6:2a00:7540:1::5])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mail.norma.perm.ru",
 Issuer "Vivat-Trade UNIX Root CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id DE32B1D04
 for <freebsd-stable@freebsd.org>; Wed, 23 Sep 2015 16:56:41 +0000 (UTC)
 (envelope-from emz@norma.perm.ru)
Received: from [192.168.248.35] ([192.168.248.35])
 by elf.hq.norma.perm.ru (8.14.9/8.14.9) with ESMTP id t8NGuYdu021392
 for <freebsd-stable@freebsd.org>; Wed, 23 Sep 2015 21:56:35 +0500 (YEKT)
 (envelope-from emz@norma.perm.ru)
Subject: Re: when the sshd hits the fan
To: freebsd-stable@freebsd.org
References: <56026686.8030308@norma.perm.ru> <86wpvhjm7g.fsf@nine.des.no>
 <5602C0C2.5010102@norma.perm.ru>
 <EA745BDC-F5F1-4C8F-9B43-E0FE86B0AEA8@slsware.net>
From: "Eugene M. Zheganin" <emz@norma.perm.ru>
Message-ID: <5602D9B9.6070206@norma.perm.ru>
Date: Wed, 23 Sep 2015 21:56:25 +0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <EA745BDC-F5F1-4C8F-9B43-E0FE86B0AEA8@slsware.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (elf.hq.norma.perm.ru [192.168.3.10]); Wed, 23 Sep 2015 21:56:36 +0500 (YEKT)
X-Spam-Status: No hits=-102.9 bayes=0.0000 testhits ALL_TRUSTED=-1,
 BAYES_00=-1.9,USER_IN_WHITELIST=-100 autolearn=ham autolearn_force=no
 version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on elf.hq.norma.perm.ru
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2015 16:56:42 -0000

Hi.

On 23.09.2015 20:35, Glenn English 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?
>
Because in the case of remote server the absence of sshd can prevent yoy 
from loggin for several minutes, even dozens of minutes, and this can be 
pretty harmful in a production environment.

Eugene.