Issue #794 has been updated by Clément OUDOT. Target version set to 2.2
---------------------------------------- Feature #794: logging enhancement : mention task source and destination connection explicitly http://tools.lsc-project.org/issues/794 Author: Martin H Status: New Priority: Low Assigned to: Category: Core Target version: 2.2 Hi, When dealing with multiple connectors and multiple directory, it could be useful to have source and destination connection explicitly mentioned in logs files so you can't get lost in the sync direction and path. For example : <pre> Oct 01 10:59:09 - INFO - Connecting to LDAP server ldap://xxx/... as .... Oct 01 10:59:09 - INFO - Connecting to LDAP server ldap://yyy/... as .... Starting sync for user ... </pre> (NB : you could even add the work 'task' in above statement 'Starting sync for user' , because 'user' is a task. If one doesn't know LSC, just by reading the logs he might not get it.) Then I would suggest to print a destination/source info for the task here (maybe in DEBUG level ?) : <pre> [timestamp] - LEVEL - task 'user' : ldapSourceService name='...', conref='...' with url='...' [timestamp] - LEVEL - task 'user' : ldapDestinationService name='...', conref='...' with url='...' </pre> Same thing could be applied in LDIF logging output, for example by adding in comment : <pre> # by task 'user' # ldapSourceService name='...', conref='...' with url='...' # ldapDestinationService name='...', conref='...' with url='...' dn: ... changetype: ... </pre> -- 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
