Section 9 : Miscellaneous Stuff

Q906: Year 2000 compliance of HylaFAX?

Q.

What is the status of HylaFAX's Year 2000 compliance?

A.

Update
A bug has been found causing HylaFAX not to think that the year 2000 is a leap year when queueing jobs using the at syntax. A patch is available, leap-year.patch.

Original answer
HylaFAX has no known Year 2000 issues. There is some date handling in non critical parts of the Server but whether this causes problems is at least partly dependent on the operating system. The best way to ensure uninterrupted service is to test the application thoroughly beforehand.

In summary: HylaFAX has not being known to fail any testing sofar, but there is NO guarantee of Year 2000 compliance"

Some experiences of a mailing list subscriber may also be useful:

From: Ken Robinson
Subject: RE: flexfax: Year 2000 Status Of Hylafax
Date: Thu, 18 Feb 1999 16:23:26 -0500

    Given that Hylafax is freeware, I highly doubt that SGI will release an
    official statement with Y2K compliance and hylafax.

    However, with hylafax itself, it'll run just fine no matter what the date.
    I put it through Y2K testing myself a few months ago, and, it ran with
    flying colors.  (version 4.0pl2)

    The main issue that remains is dealing with the xferlog file.  If you are
    parsing out the data and using it elsewhere, there may be a problem there,
    in that the year is just two digits.  If not, there is no problem that i
    could detect.

    -Ken
    

FAQ Index