From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jelle Licht <jlicht@fsfe.org>
Subject: bug#37309: =?UTF-8?Q?=E2=80=98ssh-daemon=E2=80=99?= service fails to
 start at boot
Date: Tue, 26 Nov 2019 19:34:52 +0100
Message-ID: <87y2w2mqpf.fsf@jlicht.xyz>
References: <87k1da6fdb.fsf@roquette.mug.biscuolo.net>
 <87y315t3hw.fsf@roquette.mug.biscuolo.net>
 <87tvbhra2v.fsf@roquette.mug.biscuolo.net> <87imrvhhpy.fsf@cbaines.net>
 <874l3crjqr.fsf@roquette.mug.biscuolo.net>
 <87k1c6p914.fsf@roquette.mug.biscuolo.net> <20190817152031.GA3191@jurong>
 <87pnkuyac0.fsf_-_@gnu.org> <20190828181141.GA27765@jurong>
 <87ef0u2867.fsf@roquette.mug.biscuolo.net> <871rwro1x9.fsf@member.fsf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:56044)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1iZffz-0004We-D5
 for bug-guix@gnu.org; Tue, 26 Nov 2019 13:35:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1iZffy-0004At-AI
 for bug-guix@gnu.org; Tue, 26 Nov 2019 13:35:03 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:46960)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1iZffy-0004Al-6g
 for bug-guix@gnu.org; Tue, 26 Nov 2019 13:35:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1iZffy-0007Lc-46
 for bug-guix@gnu.org; Tue, 26 Nov 2019 13:35:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.37309.B37309.157479329928232@debbugs.gnu.org>
In-Reply-To: <871rwro1x9.fsf@member.fsf.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: =?UTF-8?Q?=E5=AE=8B=E6=96=87=E6=AD=A6?= <iyzsong@member.fsf.org>, Giovanni Biscuolo <g@xelera.eu>
Cc: 37309@debbugs.gnu.org

Hey =E5=AE=8B=E6=96=87=E6=AD=A6, Giovanni,

iyzsong@member.fsf.org (=E5=AE=8B=E6=96=87=E6=AD=A6) writes:

> [...]
> Yes, I think when 'ssh-daemon' failed to start, shepherd should respawn
> it until success or disable it, but by look at the code of
> 'make-forkexec-constructor', when using 'pid-file' (as 'ssh-ademon'
> does), and a timeout (default to 5s %pid-file-timeout) is reached, the
> processes got a 'SIGTERM' and return '#f' as its running state, which
> won't be respawn (it's not a pid number) I guess...
>
> To ludo: Is my analysis correct?  It's not clear to me how to fix it so
> 'ssh-daemon' can be respawn though...

I think I am also running into a similar issue on my spinning rust based
T400. Is there a workaround available that does the above, or is that
analysis of the situation not correct either?

Thanks,

Jelle