Conversation

Notices

1. Embed this notice
   casey is remote (realcaseyrollins@noauthority.social)'s status on Tuesday, 17-Dec-2024 00:59:45 JST casey is remote

   • Yogthos

   @yogthos Yep this is why I almost always reboot

   • Embed this notice
     djsumdog (djsumdog@djsumdog.com)'s status on Tuesday, 17-Dec-2024 00:59:45 JST djsumdog

     in reply to

     • Yogthos

     restarting sshd should keep your existing session open with the old daemon, while the new daemon binds to the listening port.

   • Embed this notice
     djsumdog (djsumdog@djsumdog.com)'s status on Tuesday, 17-Dec-2024 05:31:51 JST djsumdog

     in reply to

     • Andrew Nitrogenesis
     • Yogthos
     I got that a little wrong. The daemon forks a child process for each connection. So when you restart the daemon, your connection is already part of a detached child-process. Your existing sshd session uses the old version in memory, but new connections will be forked from the new process.
   • Embed this notice
     Andrew Nitrogenesis (nitrogenez@pl.m0e.space)'s status on Tuesday, 17-Dec-2024 05:31:52 JST Andrew Nitrogenesis

     in reply to

     • djsumdog
     • Yogthos
     @djsumdog
     i can guess, why, but why?
     @realcaseyrollins @yogthos