Re: restricting slapd memory consumption

[Ralf Narozny <rnarozny@web.de>]

Hi,

Pierangelo Masarati schrieb:
> Buchan Milne wrote:
>
> > /me notes that it would be nice to have more detail on the entry 
> > cache available via back-monitor, such as the number of entries in 
> > the cache, and the amount of entry cache that is used ...
>
> Something like
>
> bash-3.1$ ldapsearch -x -H ldap://:9011 -b 'cn=Databases,cn=Monitor' \
>     '(objectclass=olmBDBDatabase)' @olmBDBDatabase


I configured the slapd to create a monitor, but the information you want 
is not present.

Maybe I missed something to configure, but the manual is not too 
thouroughly written by now ;-)

database monitor
rootdn         "cn=root,cn=monitor"
rootpw         {SSHA}...

ldapsearch -D 'cn=root,cn=monitor' -W -b 'cn=Databases,cn=Monitor' 
'objectclass=*' '*' '+'

(as far as I understood, this should show all data for the entries below 
cn=Databases,cn=Monitor')

# extended LDIF
#
# LDAPv3
# base <cn=Databases,cn=Monitor> with scope subtree
# filter: objectclass=*
# requesting: * +
#

# Databases, Monitor
dn: cn=Databases,cn=Monitor
objectClass: monitorContainer
structuralObjectClass: monitorContainer
cn: Databases
creatorsName: cn=root,cn=monitor
modifiersName: cn=root,cn=monitor
createTimestamp: 20080401132535Z
modifyTimestamp: 20080401132535Z
description: This subsystem contains information about configured databases.
readOnly: FALSE
namingContexts: cn=config
namingContexts: o=our
monitorContext: cn=Monitor
entryDN: cn=Databases,cn=Monitor
subschemaSubentry: cn=Subschema
hasSubordinates: TRUE

# Database 0, Databases, Monitor
dn: cn=Database 0,cn=Databases,cn=Monitor
objectClass: monitoredObject
structuralObjectClass: monitoredObject
cn: Database 0
monitoredInfo: config
monitorIsShadow: FALSE
creatorsName: cn=root,cn=monitor
modifiersName: cn=root,cn=monitor
createTimestamp: 20080401132535Z
modifyTimestamp: 20080401132535Z
namingContexts: cn=config
readOnly: FALSE
seeAlso: cn=Backend 0,cn=Backends,cn=Monitor
entryDN: cn=Database 0,cn=Databases,cn=Monitor
subschemaSubentry: cn=Subschema
hasSubordinates: FALSE

# Database 1, Databases, Monitor
dn: cn=Database 1,cn=Databases,cn=Monitor
objectClass: monitoredObject
structuralObjectClass: monitoredObject
cn: Database 1
monitoredInfo: bdb
monitorIsShadow: FALSE
creatorsName: cn=root,cn=monitor
modifiersName: cn=root,cn=monitor
createTimestamp: 20080401132535Z
modifyTimestamp: 20080401132535Z
namingContexts: o=our
readOnly: FALSE
labeledURI:: 
ZmlsZTovLy91c3IvbG9jYWwvZnJlZW5ldC9sZGFwL3Zhci9sZGFwL29wZW5sZGFwL
WRhdGEvAC8=
seeAlso: cn=Backend 2,cn=Backends,cn=Monitor
entryDN: cn=Database 1,cn=Databases,cn=Monitor
subschemaSubentry: cn=Subschema
hasSubordinates: FALSE

# Database 2, Databases, Monitor
dn: cn=Database 2,cn=Databases,cn=Monitor
objectClass: monitoredObject
structuralObjectClass: monitoredObject
cn: Database 2
monitoredInfo: monitor
monitorIsShadow: FALSE
creatorsName: cn=root,cn=monitor
modifiersName: cn=root,cn=monitor
createTimestamp: 20080401132535Z
modifyTimestamp: 20080401132535Z
monitorContext: cn=Monitor
readOnly: FALSE
seeAlso: cn=Backend 5,cn=Backends,cn=Monitor
entryDN: cn=Database 2,cn=Databases,cn=Monitor
subschemaSubentry: cn=Subschema
hasSubordinates: FALSE

# search result
search: 2
result: 0 Success

# numResponses: 5
# numEntries: 4