Issue 64 - Y2k compatibility
Summary: Y2k compatibility
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1999-02-02 19:01 UTC by Frank Henderson
Modified: 2014-08-01 21:06 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Henderson 1999-02-02 19:01:23 UTC 
I saw on the discussion lists several mentions of patches to a time 
function to correct y2k problems but then they mentioned these changes
were in the -devel just not -stable release.  As these messages were from
October 1998, I was womdering what the y2k status is (especially 1.1.1
which
I'm now using).

thanks,
-- 
# Frank Henderson               |             hendefd@mail.auburn.edu
# Network Services             /0\                   Slapd/Ldap Admin
# Auburn University  \_______[|(.)|]_______/
# DUC Postmaster       o   ++   0   ++   o
Comment 1 Kurt Zeilenga 1999-02-02 19:47:55 UTC 
At 07:01 PM 2/2/99 GMT, account@mail.auburn.edu wrote:
>I saw on the discussion lists several mentions of patches to a time 
>function to correct y2k problems but then they mentioned these changes
>were in the -devel just not -stable release.  As these messages were from
>October 1998, I was womdering what the y2k status is (especially 1.1.1
>which
>I'm now using).

Those changes were included in OpenLDAP 1.1.  That is the slapd
server, by default, records the creation/modified timestamps
using the full integer value of the year (not just the last
two digits) AND uses GMT.

Kurt
Comment 2 Kurt Zeilenga 1999-02-03 23:25:12 UTC 
changed notes
changed state Open to Closed
Comment 3 OpenLDAP project 2014-08-01 21:06:05 UTC 
questions aren't issues