Hi! I just post this as a kind of backup or reminder, so future searches will lead to the solution. It is possible to change the openssh version on the fly without cutting existing connections. One just moves the old crap to another place, installs the new binaries and everything is fine. When users log out and in again they are using the new version without any further pain. This works only if You kill -15 the master sshd (the childs stay alive) If You do not kill it, You will get error messages of the form: # /opt/openssh-2.9.9p2/sbin/sshd -d [...] debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA debug1: Bind to port 22 on ::. debug1: Bind to port 22 on 0.0.0.0. Cannot bind any address. Took me quite a while to find out I forgot to kill the old one. feature request: sshd detects a concurring sshd is running and gives an appropriate error message. Markus
i think the message is already very appropriate. On Fri, Oct 05, 2001 at 09:08:05AM +0200, Markus Werle wrote:> Hi! > > I just post this as a kind of backup or reminder, > so future searches will lead to the solution. > > It is possible to change the openssh version > on the fly without cutting existing connections. > One just moves the old crap to another place, > installs the new binaries and everything is fine. > > When users log out and in again they are > using the new version without any further pain. > > This works only if You kill -15 the master sshd > (the childs stay alive) > If You do not kill it, You will get error messages of the > form: > > # /opt/openssh-2.9.9p2/sbin/sshd -d > [...] > debug1: read PEM private key done: type DSA > debug1: private host key: #2 type 2 DSA > debug1: Bind to port 22 on ::. > debug1: Bind to port 22 on 0.0.0.0. > Cannot bind any address. > > Took me quite a while to find out I forgot to kill > the old one. > > feature request: > sshd detects a concurring sshd is running and gives an > appropriate error message. > > > Markus >
On Fri, 5 Oct 2001, Markus Werle wrote: :# /opt/openssh-2.9.9p2/sbin/sshd -d :[...] :debug1: read PEM private key done: type DSA :debug1: private host key: #2 type 2 DSA :debug1: Bind to port 22 on ::. :debug1: Bind to port 22 on 0.0.0.0. :Cannot bind any address. : :Took me quite a while to find out I forgot to kill :the old one. : :feature request: :sshd detects a concurring sshd is running and gives an :appropriate error message. are you using linux? you should have seen something like: debug1: Bind to port 22 on ::. Bind to port 22 on :: failed: Address already in use. debug1: Bind to port 22 on 0.0.0.0. Bind to port 22 on 0.0.0.0 failed: Address already in use. Cannot bind any address. where the address already in use gives additional information. see this thread for details: http://marc.theaimsgroup.com/?t=98241837100002&w=2&r=1