|
 OpenLDAP Faq-O-Matic : Trash :
 Is OpenLDAP Software ready for the year 2000? |
This question is likely a bit moot, but, yes,
OpenLDAP Software is ready for the year 2000.
|
|
LDAP, itself, defines a number of attribute types which represent
time. These include createtimestamp and modifytimestamp.
The times are represented in Generalized Time as specified in X.208, for
example: 199412161032Z. OpenLDAP generates time strings
that conform to this syntax. Directory Administrators SHOULD use
attribute types of Generalized Time syntax to represent dates.
LDAP has a historical date format known as UTC Time which syntax
does not include the century. OpenLDAP does not directly use this
syntax. However, some historical applications may use attribute types
of this syntax. Such applications should be rewritten to use generalized
time syntax. Directory Administrators SHOULD avoid use of attribute types
of UTC Time syntax to represent dates.
|
| OpenLDAP uses time_t to represent time. Operating systems
define time_t such that it can represent time while into
the future. On most UNIX systems with 32-bit time_t, an overflow
will not occur until the year 2038.
It's believed that such systems will upgrade to a 64-bit time_t
long before any rollover occurs.
For additional information about Unix (and Unix-like) date issues, see:
FreeBSD Y2K (http://www.freebsd.org/y2kbug.html)
Linux Y2K (http://www.linux.org.uk/mbug.html)
|
If you discover a year 2000 problem, please file an bug report
using our Issue Tracking System (http://www.openldap.org/its/).
|
| [Append to This Answer] |
Kurt@OpenLDAP.org
|