Univention Bugzilla – Bug 28618
lock.schema: lockTime ORDERING integerOrderingMatch
Last modified: 2020-07-04 07:08:43 CEST
Für das lockTime-Attribut ist im lock.schema leider kein ORDERING definiert, weshalb eine Suche der Form univention-ldapsearch -xLLL "(&(objectClass=lock)(lockTime<=$(date +%s)))" nicht funktioniert, um alle inzwischen abgelaufenen Locks zu finden. Siehe <http://www.zytrax.com/books/ldap/ch3/#attributes> für Literatur dazu. diff --git a/branches/ucs-3.1/ucs/management/univention-ldap/schema/lock.schema b/branches/ucs-3.1/ucs/management/univention-ldap/schema/lock.schema index e154eb4..51546fb 100644 --- a/branches/ucs-3.1/ucs/management/univention-ldap/schema/lock.schema +++ b/branches/ucs-3.1/ucs/management/univention-ldap/schema/lock.schema @@ -28,6 +28,7 @@ attributetype ( 1.3.6.1.4.1.10176.92 NAME 'lockTime' DESC 'time the lock was set in place in seconds since epoch' EQUALITY integerMatch + ORDERING integerOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 ) objectclass ( 1.3.6.1.4.1.10176.94 NAME 'lock' Und wer die Datei anfasst darf auch bitte gleich die Leerzeichen durch Tabs ersetzen.
This issue has been filed against the UCS version "unstable" which does not really exist. Please change the version value.
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.