From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 08:34:37 2003 Return-Path: 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 3BDB116A4BF for ; Mon, 22 Sep 2003 08:34:37 -0700 (PDT) Received: from mail-efg0.york.ac.uk (mail-efg0.york.ac.uk [144.32.128.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 020BA43FD7 for ; Mon, 22 Sep 2003 08:34:36 -0700 (PDT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from willow (willow.csrv.ad.york.ac.uk [144.32.226.5]) by mail-efg0.york.ac.uk (8.12.9/8.12.9) with ESMTP id h8MFYODZ026286; Mon, 22 Sep 2003 16:34:24 +0100 (BST) From: "Gavin Atkinson" To: "'Pete French'" , Date: Mon, 22 Sep 2003 16:34:25 +0100 Message-ID: <001101c3811f$00e25cb0$05e22090@csrv.ad.york.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Importance: Normal In-Reply-To: X-York-MailScanner: Found to be clean Subject: RE: Very slow SSh since upgrading machines to RELENG_4_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 15:34:37 -0000 > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Pete French > Sent: 22 September 2003 15:54 > > but if I try and ssh between two machines in Jersey then ssh pauses for > a considerable length of time before letting me in. By "considerable" > I mean over a minute. > > Preseumably the far end is trying to do something and then timing out, > but the question is *what* is it doing and how do I fix it ? Also > why did this only change when I upgraded ? This sounds suspiciously like DNS timing out. I seem to remember this is due to the fact the default config of sshd now enables privilege seperation. sshd chroots into /var/empty and therefore can't access /etc/hosts, /etc/nsswitch.conf, /etc/resolv.conf etc. See, for example, http://www.freebsd.org/cgi/getmsg.cgi?fetch=509623+513499+/usr/local/www /db/text/2003/freebsd-stable/20030323.freebsd-stable Gavin