GNU bug report logs - #37309
'ssh-daemon' fails to start

Previous Next

Full log

Message #17 received at 37309 <at> debbugs.gnu.org (full text, mbox):

From: Jelle Licht <jlicht <at> fsfe.org>
To: 宋文武 <iyzsong <at> member.fsf.org>, Giovanni Biscuolo
 <g <at> xelera.eu>
Cc: 37309 <at> debbugs.gnu.org
Subject: Re: bug#37309: ‘ssh-daemon’ service fails
 to start at boot
Date: Tue, 26 Nov 2019 19:34:52 +0100

Hey 宋文武, Giovanni,

iyzsong <at> member.fsf.org (宋文武) 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.