On 5/28/24 09:38, Samuel Sieb wrote:
There is nothing to fix. The ssh process has already loaded the libraries, so it won't crash if you replace them. After you upgrade the libraries, you just need to restart it to get the new ones loaded. Any existing connections will still be processes running with the old libraries. What exactly are you expecting?
I am expecting exactly what you have described, but the first mail in this thread is claiming an inability to fork, and that is (we are stating the same thing!) not expected. Why is the original poster saying that he is not able to reach the machine during the upgrade because of inability to fork sshd? I've become suspicious of maybe dlopen tricks failing near the moment a new connection triggers a fork, which would be interesting to be aware of, if any such case. (note that you say "any existing connections" uses the old libraries, but indeed also new connections will use the old libraries, if the restart has not been done yet, so the claimed issue should definitely never happen) Regards. -- Roberto Ragusa mail at robertoragusa.it -- _______________________________________________ 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
