Re: [Multisync-users] ldap??

[Niels Christian �rgaard]

Thank you - I'd almost given up, but your mail made me try my hand with the ldap* tools :)

I did

"ldapsearch -D cn=admin,dc=durex -h localhost -w ***** -x -b dc=durex | grep -A 3 -B 3 admin"
"ldapmodify -D cn=admin,dc=durex -h localhost -w ***** -x"

and fed the output to which, from what I gathered from the man-pages, should result in the admin-user being re-added by the ldap* tools and thus recieving a timestamp.
Feel free to correct me if I'm mistaken (I prolly am), but it appears to work. Now I just need to figure out why multisync tends to crash the first time I ask it to sync using ldap.

Cheers, and once again "thanx"
/Nc.



On Fri, 2004-04-30 at 19:21, Armin Bauer wrote:

the problem here is that the admin entry was initially added by slapadd.
slapadd is a tool which works directly! on the database file, whereas
ldapadd uses talks to the server. The server adds a timestamp to every
entry that is added, slapadd doesnt do this. without this stamp it is
impossible to sync since you can never know when the entry was modified.

You should search for a solution which adds the missing stamps to the
contacts.

> Heya 
> 
> I'm trying to get the LDAP-plugin to work, but it seems to dislike my
> slapd:
> 
> [remote] ERROR: Loaded entry cn=admin,dc=durex missing modifyTimestamp.
> Impossible to sync that. don't use slapadd, use ldapadd!
> [remote] ERROR: Loaded entry cn=admin,dc=durex missing modifyTimestamp.
> Impossible to sync that. don't use slapadd, use ldapadd!
> 
> The entries in the slapd are added by eighter Evolution or Multisync so
> I have little chance to follow the above "suggestion". Any pointers on
> how to get it to sync (even just to copy the entries from my evolution
> to the slapd - it has copied ~80%, and fails to update or continue) are
> most welcome, as we are trying to built a central directory of contacts.
> 
> Cheers,
>  /Nc.

-- 
for(;!sleep();sheep++)

signature.asc
Description: This is a digitally signed message part