From owner-freebsd-bugs Thu Aug 8 12:20:14 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0211C37B400 for ; Thu, 8 Aug 2002 12:20:10 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41EE543E70 for ; Thu, 8 Aug 2002 12:20:09 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g78JK8JU096764 for ; Thu, 8 Aug 2002 12:20:08 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g78JK8kA096763; Thu, 8 Aug 2002 12:20:08 -0700 (PDT) Date: Thu, 8 Aug 2002 12:20:08 -0700 (PDT) Message-Id: <200208081920.g78JK8kA096763@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Stefan Schwarzer Subject: Re: misc/41213: top(1) blocks if NIS-related entries in passwd(5) are in a certain order Reply-To: Stefan Schwarzer Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR misc/41213; it has been noted by GNATS. From: Stefan Schwarzer To: David Malone Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/41213: top(1) blocks if NIS-related entries in passwd(5) are in a certain order Date: Thu, 08 Aug 2002 21:14:23 +0200 Hello David David Malone wrote: > This might be a bug in the code for iterating through all users > in libc. I think that top tries to do this to find the longest > username it will have to deal with. Could you try the included > simple C program and see if you can reproduce the problem? It should > keep looping on the problem user. I've tried the program with my workaround applied and for two different positions of the netgroup entry I spoke of. For the latter two of the three positions, the program loops. > If you want to check it is this code that is looping, the last thing > before top gets stuck in a loop should be the calling of sysctlbyname > on either "machdep.smp_active" or "smp.smp_active". You may be able > to find this in your ktrace output. I couldn't find that, however (searching the dump in less for sysctlbyname). Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message