Bug 124363 (DEFECT000302240)

Summary:	Events: The LDAP monitorEvents.c sample pegs the CPU at 100% usage.
Product:	[Novell Products] NDS SDK	Reporter:	Dave Steck <dsteck>
Component:	LDAP C SDK	Assignee:	Jeff Vincent <jvincent>
Status:	VERIFIED FIXED	QA Contact:	Sundar Swamy <ssundar>
Severity:	Minor
Priority:	P5 - None	CC:	aclark
Version:	OCT 2006 NDK	Keywords:	English
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Rajkumar V 2005-10-10 22:54:42 UTC



------- Bug moved to this database by vrajkumar@novell.com 2005-10-10 16:54 -------

This bug previously known as bug DEFECT000302240 at remedy/
remedy/show_bug.cgi?id=DEFECT000302240
Originally filed under the NDS SDK product and LDAP C SDK component.

---------
<remedy_version_found_in> BLANK </remedy_version_found_in>
---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> Because it calls ldap_result with a timeout of {0.0},
      it's in a tight polling loop.
If we call it with a timeout of 5 or 10 seconds, we still get events back as
soon as they happen, but the CPU is freed.  This lets the app wake up often
enough to check for an exit condition.  Since people will copy the example,
we should show the better way. </remedy_details>