Date: Thu, 14 Jan 1999 22:58:15 -0700 From: Warner Losh <imp@village.org> To: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au> Cc: danny@hilink.com.au, committers@FreeBSD.ORG Subject: Re: Y2K compliance question Message-ID: <199901150558.WAA21153@harmony.village.org> In-Reply-To: Your message of "Fri, 15 Jan 1999 13:46:39 %2B1100." <99Jan15.134603est.40357@border.alcanet.com.au> References: <99Jan15.134603est.40357@border.alcanet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <99Jan15.134603est.40357@border.alcanet.com.au> Peter Jeremy writes: : I'm having a quick check and I've found what seem to be problems in: : CVSROOT/edithook : doc/ja/man/man1/date.1 : src/contrib/cvs/contrib/log.pl : src/contrib/cvs/contrib/log_accum.pl : src/contrib/cvs/contrib/sccs2rcs.csh : src/contrib/groff/doc/meref.me : src/contrib/sendmail/contrib/mmuegel : src/share/doc/usd/20.meref/ref.me : src/share/me/summary.external : src/usr.sbin/adduser/adduser.perl I'm just looking at the 'c' files. Others should look upon these. : src/gnu/usr.bin/rcs/lib/rcstime.c : src/gnu/usr.bin/rcs/lib/rcstime.c I see no Y2K problems here. All uses of tm_year assume that it measures years since 1900, which is correct. It further assumes that all 2 digit dates are in 1900..1999, which is also correct for this file because it parses dates stored in the RCS file itself. It stores dates in the file from 1900..1999 w/o the leading 19 for historical comapatability reasons. What have I missed? : src/release/picobsd/tinyware/simple_httpd/simple_httpd.c I see no Y2K problems here. All dates are logged as two digit numbers. The century is know from the context. : src/usr.bin/fetch/http.c There appears to be a minor nit in parsing two digit dates. It appears to assume that they are in 1900..1999. I don't know if this is on purpose and specified in the http spec for backward compatability, or if it is just slightly sloppy programming when it gets two digit dates back from the server. It appears to go to great lengths most other places to properly handle 4 digit dates. : src/usr.sbin/cron/lib/misc.c No bugs found, although dates in mail headers are always two digits. This seems acceptible given that there is a small chance for confusion about when the date happened. : src/usr.sbin/i4b/isdndecode/layer3_subr.c : src/usr.sbin/i4b/isdntrace/q931.c I'll leave these to the isdn people. : src/usr.sbin/tcpdump/tcpslice/tcpslice.c User specified dates with 2 digits assume 1900..1999. Fixed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901150558.WAA21153>