[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34580: Service ssh-daemon could not be started
|
From: |
Danny Milosavljevic |
|
Subject: |
bug#34580: Service ssh-daemon could not be started |
|
Date: |
Sat, 28 Sep 2019 20:31:31 +0200 |
On second thought, maybe it would be easiest to make term-auto "succeed" when
it can't find that serial console. Shepherd would think everything is a-ok and
nobody would tell it any better :P
pgpyBnAuhvJuk.pgp
Description: OpenPGP digital signature
- bug#34580: Service ssh-daemon could not be started, Brant Gardner, 2019/09/20
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/24
- bug#34580: Service ssh-daemon could not be started, Brant Gardner, 2019/09/24
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/26
- bug#34580: Service ssh-daemon could not be started, Brant Gardner, 2019/09/27
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Brant Gardner, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, pelzflorian (Florian Pelz), 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Danny Milosavljevic, 2019/09/28
- bug#34580: Service ssh-daemon could not be started,
Danny Milosavljevic <=
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Brant Gardner, 2019/09/29
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/28