Issue #675 has been updated by Clément OUDOT.
Clément OUDOT wrote: > Raphaël Ouazana wrote: > > Fixed in trunk. Please test and merge on 2.1 if OK. > > It's better, but it still count 2 entries in the first counter (All entries) > for 1 modified entry. > > For example, I have 3 entries in my branch, so the counter starts at 3: > [...] > > I apply a modification, and the result is: > [...] > > The first counter should be set to 4, and not 5. My mistake, the above result is generated because I have a condition to ignore some modifications, but they are detected in "All entries" counter, which is the expected behaviour. The code can be applied to 2.1 and the ticket closed. ---------------------------------------- Bug #675: Incorrect values reported by AbstractSynchronize.getTaskStatus() method for tasks running in async mode http://tools.lsc-project.org/issues/675 Author: Manuel BOSSANT Status: Assigned Priority: Normal Assigned to: Raphaël Ouazana Category: Core Target version: 2.1 Problem in version: 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. 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 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
