Dnia Fri, May 24, 2024 at 01:33:44PM +0200, Marius Schwarz napisał(a): > Am 24.05.24 um 12:01 schrieb Roberto Ragusa: > > On 5/22/24 16:33, Marius Schwarz wrote: > > > > > So, atm, the server has a sshd that says, that openssl is newer as > > > the required openssl version. It does not start it nor can the > > > running sshd, that runs the upgrade connection, fork a new instance. > > > In other words: no login possible to rescue or recover the upgrade > > > session remotely. > > > > Why can't sshd fork a new instance? > > you have ask the sshd devs. > > First guess: they do not use fork(). The whole premise of this thread comes from doing incorrect, unsupported system upgrade on live system. Look, this method is even described with red Warning frame: https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-release/#_can_i_upgrade_between_fedora_linux_releases_using_only_dnf There's no need to continue digressing wrt sshd behaviour. -- Tomasz Torcz Only gods can safely risk perfection, tomek@xxxxxxxxxxxxxx it's a dangerous thing for a man. — Alia -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
