From owner-freebsd-stable Sun Aug 4 22:44: 9 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 7C17337B400 for ; Sun, 4 Aug 2002 22:44:06 -0700 (PDT) Received: from arutam.inch.com (ns.inch.com [216.223.192.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9B9843E6A for ; Sun, 4 Aug 2002 22:44:05 -0700 (PDT) (envelope-from spork@inch.com) Received: from inch.com (inch.com [216.223.192.20]) by arutam.inch.com (8.12.2/8.12.2/UTIL-INCH-3.0.6) with ESMTP id g755i5CA018323; Mon, 5 Aug 2002 01:44:05 -0400 (EDT) Date: Mon, 5 Aug 2002 01:44:05 -0400 (EDT) From: Charles Sprickman To: CHOI Junho Cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: remote upgrade stops ssh connections In-Reply-To: <20020805.143230.106797934.cjh@kr.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 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). 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. Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message