From owner-freebsd-stable Mon Jan 15 11:16:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id AE73437B400 for ; Mon, 15 Jan 2001 11:16:22 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id TAA67801 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 19:16:21 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101151916.TAA67801@ns.a1.org.uk> Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP In-Reply-To: <3A63484B.6E0D1253@ufl.edu> from Bob Johnson at "Jan 15, 2001 01:58:19 pm" To: freebsd-stable@freebsd.org Date: Mon, 15 Jan 2001 19:16:21 +0000 (GMT) Reply-To: freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bob Johnson wrote: > I just upgraded a system to 4.2-STABLE and it does indeed have a > new sshd entry in /etc/pam.conf. You need to add that to your > pam.conf. > > In general, you need to run mergemaster after upgrading. It steps > through the various configuration files, shows you which ones have > changed, and helps you merge your customizations into the new > versions. > > - Bob Yes, but there was an "issue" sometime on Friday that was sorted by Sat lunch. I always run mergemaster, but I was hit with this one too. Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message