Hi,
Can you please open an issue so we can track this down?
Regards,
Raphaël Ouazana.
Le 12/03/2014 16:03, bossant a écrit :
I'm sure not so many modifications were done by reading the lsc.ldif
log file.
The counter is incremented even if no modifications were made in line
#579 in AbstractSynchronize.run() method, no?
Manuel.
On Wed, 12 Mar 2014 13:52:39 +0100, Clément OUDOT wrote:
2014-03-12 11:09 GMT+01:00 bossant :
Hi,
Im using lsc agent to monitor LSC status. In particular Nagios
check retrieves task status.
I noticed that it returns very huge numbers for All entries field,
for example:
All entries: 3240836, to modify entries: 97, successfully modified
entries: 97, errors: 0
My LDAP and database do not contain so many users.
There are 2 calls to incrementCountAll() method in
AbstractSynchronize.run() method.
The first one might be the explanation of this huge number as I run
my task in asynchronous mode - so I think run() is called every 5
seconds.
I also see that no provision is done in incrementCount methods
about integer overflow...
Right,
for now, the counter is incremented for each modificiation, so in
async mode, if one entry is modified 10 times, the "all entries"
counter will grow of 10.
For the integer overflow, could you maybe open an issue and propose a
patch?
Clément.
Links:
------
[1] mailto:[email protected]
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
