Blind guess: you are using debian, systemd killed sshd 'cause ssh did not get enough random data ... guess you run it on a rpi? Nik Anno domini 2019 Thu, 8 Aug 03:32:14 -0400 Gene Heskett scripsit: > Greetings; > > And I had just had it update everything, 162 of the 165 packages being > from TDE. > > From here, all indications of an extended to 20 minutes e2fsck or > something. No response to a ping, no response to an attempted ssh -Y > alias login. So I slip on a t-shirt and stumble out to the machine at > 3AM, to be greeted by its own login greeter. So I logged in, all normal. > > And now that I'm logged in there, everything else is also working > normally. > > So its own login has been moved up early so nothing in the way of > services is running until after the local login. > > This. to be blunt, is a disaster for the way I have normally worked to > maintain these machines for over a decade. > > Can this be unfixed? Its a right pain in the ass to be locked out of a > machine because the local login hasn't been done. > > Cheers, Gene Heskett -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
