From owner-freebsd-bugs@FreeBSD.ORG Tue Jun 26 21:00:16 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87A8016A400 for ; Tue, 26 Jun 2007 21:00:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 2FC5B13C448 for ; Tue, 26 Jun 2007 21:00:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l5QL0Fp5073079 for ; Tue, 26 Jun 2007 21:00:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l5QL0FA5073078; Tue, 26 Jun 2007 21:00:15 GMT (envelope-from gnats) Date: Tue, 26 Jun 2007 21:00:15 GMT Message-Id: <200706262100.l5QL0FA5073078@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: John Flanagan Cc: Subject: Re: misc/112614: 'ls -l' is very slow or doesn't work at all X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Flanagan List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 21:00:16 -0000 The following reply was made to PR misc/112614; it has been noted by GNATS. From: John Flanagan To: bug-followup@FreeBSD.org Cc: seal@inar.ru Subject: Re: misc/112614: 'ls -l' is very slow or doesn't work at all Date: Tue, 26 Jun 2007 00:46:00 -0500 Removing all but a few users from the master password file will eliminate the extreme slowdown in ls -l response time which would suggest it is related to uid to name resolution. This is an extremely annoying issue and it is beyond belief that few if any people haven't escalated this bug to a high level. I have access to two FreeBSD 6.2 stable machines that have this problem. If anyone has a solution, fix or workaround, please share. --jpf.