Date: Mon, 2 Feb 1998 13:06:55 -0800 (PST) From: mvh@tis.com To: freebsd-gnats-submit@FreeBSD.ORG Subject: ports/5626: 'ldap' port eats all available CPU time Message-ID: <199802022106.NAA09380@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 5626 >Category: ports >Synopsis: 'ldap' port eats all available CPU time >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 2 13:10:01 PST 1998 >Last-Modified: >Originator: Michael Harding >Organization: Trusted Information Systems >Release: 2.2.5 stable >Environment: FreeBSD grendel.la.tis.com 2.2-971229-SNAP FreeBSD 2.2-971229-SNAP #0: Mon Dec 29 17:53:58 PST 1997 mvh@grendel.la.tis.com:/usr/src/sys/compile/TIS i386 >Description: If you install and configure the University of Michigan ldap server, /usr/ports/net/ldap, it will chew up all of the available CPU time, apparently spawning threads like mad. There is a patch list at http://www.critical-angle.com/ldapworld/patch/ but I don't know if this will fix the problem. >How-To-Repeat: You can run the test suite in /usr/ports/net/ldap/work/ldap-3.3/tests - by running 'top' you can see that there will be several 'slapd' ldap daemons running chewing up all of the CPU even after the test finish (and fail). >Fix: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802022106.NAA09380>