Bug 124363 (DEFECT000302240) - Events: The LDAP monitorEvents.c sample pegs the CPU at 100% usage.
Summary: Events: The LDAP monitorEvents.c sample pegs the CPU at 100% usage.
Status: VERIFIED FIXED
Alias: DEFECT000302240
Product: NDS SDK
Classification: Novell Products
Component: LDAP C SDK (show other bugs)
Version: OCT 2006 NDK
Hardware: Other Other
: P5 - None : Minor
Target Milestone: ---
Assignee: Jeff Vincent
QA Contact: Sundar Swamy
URL:
Whiteboard:
Keywords: English
Depends on:
Blocks:
 
Reported: 2002-05-24 20:24 UTC by Dave Steck
Modified: 2007-05-14 17:49 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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>