From owner-freebsd-stable Sun Aug 4 22:53: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF8FB37B400 for ; Sun, 4 Aug 2002 22:52:56 -0700 (PDT) Received: from daemon.kr.FreeBSD.org (daemon.kr.freebsd.org [211.176.62.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2C3F43E77 for ; Sun, 4 Aug 2002 22:52:55 -0700 (PDT) (envelope-from cjh@kr.FreeBSD.org) Received: from gradius.wdb.co.kr (daemon [211.176.62.31]) by daemon.kr.FreeBSD.org (Postfix) with ESMTP id 08E728F610; Mon, 5 Aug 2002 14:52:50 +0900 (KST) Received: from localhost (localhost [127.0.0.1]) by gradius.wdb.co.kr (8.12.5/8.12.3) with ESMTP id g755qlTa085989; Mon, 5 Aug 2002 14:52:47 +0900 (KST) (envelope-from cjh@kr.FreeBSD.org) Date: Mon, 05 Aug 2002 14:52:47 +0900 (KST) Message-Id: <20020805.145247.48700966.cjh@kr.FreeBSD.org> To: spork@inch.com Cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: remote upgrade stops ssh connections From: CHOI Junho In-Reply-To: References: <20020805.143230.106797934.cjh@kr.FreeBSD.org> Organization: Korea FreeBSD Users Gruop X-URL: http://www.kr.FreeBSD.org/~cjh X-Mailer: Mew version 3.0.55 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: Charles Sprickman Subject: Re: remote upgrade stops ssh connections Date: Mon, 5 Aug 2002 01:44:05 -0400 (EDT) > On Mon, 5 Aug 2002, CHOI Junho wrote: > > > At first machine, I typed "killall -1 sshd". All my session > > disconnected and I couldn't login. > > That's not surprising. Don't use killall unless you want to drop your > current connection. > > > At second machine, I typed > > "(killall -9 sshd; /usr/sbin/sshd)" and the same thing happened. > > You need not move up to a sledgehammer. > > Just kill the parent process. Try restarting it. If it doesn't restart, > investigate why by looking in the logs. Fix whatever complaint there is > in the logs (changes to sshd_config between versions, forgetting to > update your pam config file, not reading UPDATING). I used install{kernel,world} and mergemaster. sshd_config is overwritten to new one(may /usr/src/crypto/openssh/sshd_config), pam.conf is overwritten also(I didn't touch sshd_config and pam.conf before, and I usually does not touch), and UPDATING doesn't say much about this thing. > If, for example the reason it wasn't restarting was due to an error in the > config file, a reboot would do little to help you. This is not Windows, > rebooting is not the best way to fix a problem. I know. But I upgraded kernel and userland, so someday I must reboot to finalize upgrade procedure. And when I rebooted without touching anything, all problem goes out and I can login into the server without touching sshd_config or pam.conf. In my not-so-long freebsd experience it is very rare event so I am confused very much. > Charles -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho [sleeping now] [while sleeping] Korea FreeBSD Users Group Web Data Bank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message