1# -*- text -*- 2 AM-UTILS YEAR-2000 COMPLIANCE 3 4Most likely am-utils is y2k compliant. 5 6I do not know for sure because I have not certified am-utils myself, nor do 7I have the time for it. I do not think that amd will be affected by y2k at 8all, because it does not do anything with dates other than print the date on 9the log file, in whatever format is provided by your os/libc --- especially 10the ctime(3) call. 11 12However, on Friday, September 18th 1998, Matthew Crosby <mcrosby@ms.com> 13reported that they evaluated 6.0a16 and found it to be compliant. 14
| 1# -*- text -*- 2 AM-UTILS YEAR-2000 COMPLIANCE 3 4Most likely am-utils is y2k compliant. 5 6I do not know for sure because I have not certified am-utils myself, nor do 7I have the time for it. I do not think that amd will be affected by y2k at 8all, because it does not do anything with dates other than print the date on 9the log file, in whatever format is provided by your os/libc --- especially 10the ctime(3) call. 11 12However, on Friday, September 18th 1998, Matthew Crosby <mcrosby@ms.com> 13reported that they evaluated 6.0a16 and found it to be compliant. 14
|