On Sat, Feb 20, 2010 at 03:36:20PM +0000, Nuno Magalhães wrote: > Hi > > Ok, i was told sshd will keep sessions alive during an upgrade, which > would make sense since they're in memory and i'm upgrading the binary > on disk. Still, after many aptitude upgrades where the ncurses popup > tells me the following services need to be restarted, that didn't come > to mind at the time. So the idea was to run two different binaries on > two different ports with two different config files (just changing the > port (yes i opened the ports in the fw)). This is a minimal remote > server running lenny. Here's a step-by-step of what i've done, maybe > someone can shed some light on where i went wrong: > > 1. cp /usr/sbin/sshd /usr/sbin/sshd2 > 2. cp /etc/ssh/sshd_config /etc/ssh/sshd_config2 > Change the port in 2. > 3. open the new port in the fw and restart it > 4. cp /etc/init.d/ssh /etc/init.d/ssh2 > Come to think of it i don't know why i would also copy the init > script, 'cos that evidently screwed any attempt at a clean reboot. > 5. /usr/sbin/sshd2 -f /etc/ssh/sshd_config2 & > 6. test both connections > 7. wget ...debian.org...openssh-server_5.3p1-1_i386.deb > 8. dpkg -i openssh-server_5.3p1-1_i386.deb > Which produced this: > > <snip>
I missed the beginning of this thread... I just tested a couple of my machines, and I can stop the ssh daemon while logged in via ssh. My session persists, and I can restart the daemon later from that same session. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100220231951.gc5...@aurora.owens.net
