Bug 153152 - Performance improvement suggestion regarding logging
Performance improvement suggestion regarding logging
Status: CLOSED DEFERRED
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openldap (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jan Safranek
Jay Turner
: FutureFeature
Depends On:
Blocks: 153322
  Show dependency treegraph
 
Reported: 2005-04-01 16:02 EST by Brian DeFeyter
Modified: 2015-01-07 19:09 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-21 04:42:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brian DeFeyter 2005-04-01 16:02:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Description of problem:


Version-Release number of selected component (if applicable):
openldap-servers-2.2.13-2

How reproducible:
Always

Steps to Reproduce:
As far as I can tell, the default install of openldap-servers and syslog within RHEL4 has the default logging settings enabled in slapd, but no logfile defined within syslog.

Most people probably don't need all of the verbose information that would be logged via syslog by default, so all this really does is result in is a higher cpu load generated by syslog than slapd itself.

I'd suggest either tuning the logging way down, or just adding "loglevel 0" to slapd.conf as I have done to completely disable logging.

Only a suggestion..

Additional info:
Comment 1 Suzanne Hillman 2005-04-04 15:40:03 EDT
Internal RFE bug #153322 entered; will be considered for future releases.
Comment 2 Jan Safranek 2007-06-21 04:42:50 EDT
This feature request is still being evaluated by Red Hat project management.
Please use Featurezilla for discussion about the feature request.

Note You need to log in before you can comment on or make changes to this bug.