[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Backend monitoring

To: "Parvate,Girija" <parvateg@oclc.org>
Subject: Re: Backend monitoring
From: "Pierangelo Masarati" <ando@sys-net.it>
Date: Thu, 30 Sep 2004 17:57:13 +0200 (CEST)
Cc: openldap-software@OpenLDAP.org, "Ward,Eric" <warde@oclc.org>
Importance: Normal
In-reply-to: <90D12689EF7A0543AB11426D75D6ABC512D64C48@oa4-server.oa.oclc.org>
References: <90D12689EF7A0543AB11426D75D6ABC512D64C48@oa4-server.oa.oclc.org>
User-agent: SquirrelMail/1.4.3a-1

The limit is INT_MAX; further increments cause the counters to wrap (to
INT_MIN!). This is now fixed in HEAD code (see ITS#3323)
whenever openssl or gmp are available.

p.


> Hello,
> We have enabled the monitor backend for our OpenLDAP installation. We run
> version 2.1.25 with Berkeley DB 4.2.
> What is the limit for the numbers reported in cn=Monitor. What happens if
> these numbers are exceeded?
> e.g. cn=Completed,cn=Operations,cn=monitor what is the highest value for
> the
> description attribute? What happens when this number is exceeded?
> Thanks much,
> Girija Parvate
> OCLC Inc.
>


-- 
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it


    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497

References:
- Backend monitoring
  - From: "Parvate,Girija" <parvateg@oclc.org>

Prev by Date: Backend monitoring
Next by Date: Re: rootdn and sasl-regexp
Index(es):
- Chronological
- Thread