From owner-freebsd-questions@FreeBSD.ORG Tue Jul 22 11:40:28 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E68A1065691 for ; Tue, 22 Jul 2008 11:40:28 +0000 (UTC) (envelope-from sdafreebsduk@rowyerboat.com) Received: from brookes.ac.uk (csmail1.brookes.ac.uk [161.73.1.23]) by mx1.freebsd.org (Postfix) with ESMTP id D00AC8FC2F for ; Tue, 22 Jul 2008 11:40:27 +0000 (UTC) (envelope-from sdafreebsduk@rowyerboat.com) Received: from [161.73.146.9] (izb6d318.brookes.ac.uk [161.73.146.9]) (authenticated bits=0) by brookes.ac.uk (8.14.2/8.14.2) with ESMTP id m6MBeFY6018604 (SMTP-AUTH user p0036343) (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 22 Jul 2008 12:40:22 +0100 (BST) Message-ID: <4885C723.3000708@rowyerboat.com> Date: Tue, 22 Jul 2008 12:40:19 +0100 From: Stephen Allen User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Oxford Brookes University MailScanner X-MailScanner: Clean X-MailScanner-From: sdafreebsduk@rowyerboat.com X-Spam-Status: No Subject: Problem running 'top' when ldap is around X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2008 11:40:28 -0000 I've noticed that with "files ldap" in nsswitch.conf, if I try to run "top" and the ldap server is not available, it takes about a minute to start showing information, whereas normally it's instantaneous. The problem seems to be the mapping of uid numbers to usernames (the -u options prevents this). The man page says: "Normally, top will read as much of the file "/etc/passwd" as is necessary to map all the user id numbers it encounters into login names" So my question is, top must be finding a uid number that it can't match in /etc/passwd, then going on to search ldap. How can this be? Thanks, Steve :)