deadlock Message Board
[ January Full List | Reply ]

Never mind, here's the fix. Restrain the thunderous applause, please.
From Nicholas on 2 Jan '00
replying to the Perl "19100" output error posted by Nicholas

http://www.xav.com/scripts/forum.pl?read=1802

1) Search for $year in the ax-admin.cgi file and remove the 19 in front i.e. 19$term

2) scroll down in the ax.cgi file for the line that reads...

($sec,$min,$hour,$mday,$mon,$year,$wday,$yday) = localtime(time);

add a line after that which reads:

$year += 1900;

Now the code is Y2K compliant.

*********************
Note: this fix does somewhat violate the Perl logging
convention (up until now?) of writing dates as the number
of years after 1900. Where last year logs were recording
|99|, now they will be recording |2000|, rather than
|100|, which would have been the natural successor to 99.




Reply to this message

Required Details
Your name:
Subject:

Optional Details
Home page title:
Home page URL:
Email:
(if you'd like to receive automatic replies by email)

Your Message