From nobody Tue May 03 09:08:09 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 083C31AC2A69 for ; Tue, 3 May 2022 09:08:20 +0000 (UTC) (envelope-from SRS0=o5I+=VL=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KsvJL60CMz4RyW for ; Tue, 3 May 2022 09:08:18 +0000 (UTC) (envelope-from SRS0=o5I+=VL=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 541AD28411 for ; Tue, 3 May 2022 11:08:11 +0200 (CEST) Received: from illbsd.quip.test (ip-78-45-215-131.net.upcbroadband.cz [78.45.215.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 2402028417 for ; Tue, 3 May 2022 11:08:10 +0200 (CEST) Subject: Re: (263489) (D35109) freebsd-update: restart sshd after upgrade To: freebsd-current@freebsd.org References: <20b1c8ea-71ef-784f-a6bd-de1abce406a0@gmail.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <382c2b83-bd65-9534-a273-8eb17ba6aaf5@quip.cz> Date: Tue, 3 May 2022 11:08:09 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <20b1c8ea-71ef-784f-a6bd-de1abce406a0@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: cs Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4KsvJL60CMz4RyW X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of "SRS0=o5I@elsa.codelab.cz" has no SPF policy when checking 94.124.105.4) smtp.mailfrom="SRS0=o5I@elsa.codelab.cz" X-Spamd-Result: default: False [-0.65 / 15.00]; RCVD_TLS_LAST(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; NEURAL_SPAM_MEDIUM(0.08)[0.076]; NEURAL_HAM_SHORT(-0.92)[-0.923]; DMARC_NA(0.00)[quip.cz]; MLMMJ_DEST(0.00)[freebsd-current]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=o5I@elsa.codelab.cz]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; TAGGED_FROM(0.00)[=VL=quip.cz=000.fbsd]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=o5I@elsa.codelab.cz]; RECEIVED_SPAMHAUS_PBL(0.00)[78.45.215.131:received] X-ThisMailContainsUnwantedMimeParts: N On 03/05/2022 02:15, Graham Perrin wrote: > > (line 3028) > > How will freebsd-update behave in this case? > >> Cannot 'status' sshd. Set sshd_enable to YES in /etc/rc.conf or use >> 'onestatus' instead of 'status'. > > (I'd test for myself, but it's late, and I'd like to seed the thought > before I forget.) Shouldn't it be user configurable if (any) service should be restarted during update / upgrade? I remember sshd not starting after upgrade in the past. I don't use freebsd-update, but doing sshd restart by hand and sometimes there are some incompatible changes which prevent sshd from starting. This "safety" sshd restart can be dangerous too. Kind regards Miroslav Lachman