search for: unsyncronized

A few more questions and comments... related to this topic If Kerberos is the back-end to LDAP.. there is no need to synchronize or store a password in the LDAP tree.. just the principal for the user in the userpassword attribute: userpassword = {kerberos}name@domain in the smb.conf file do I need stuff like this? Unix password sync = yes passwd program =

Jonathan Higgins wrote: > > A few more questions and comments... related to this topic > > If Kerberos is the back-end to LDAP.. there is no need to synchronize or store a >password in the LDAP tree.. just the principal for the user in the userpassword >attribute: userpassword = {kerberos}name@domain That is correct. I did not mean sync between Kerberos and LDAP, I mean sync

...few years to come, hence its important that we ensure the API is extensible and as easy to make backward compatible as possible. This has led to us wanting to work hard to push through a couple of API changes that will make life easier in future: * New Time API. This is required for systems with unsyncronized TSCs like the IBM Summit systems, and is also good for variable speed CPUs (laptops) * Replacing control messages with XenBus/XenStore. Doing backwards support of the old control message API would be a *huge* pain, so we''re really keen to get this incorporated before 3.0.0. The new time...