Xref: utzoo news.sysadmin:2418 news.admin:5816
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!watmath!focsys!larry
From: larry@focsys.UUCP (Larry Williamson)
Newsgroups: news.sysadmin,news.admin
Subject: Re: question on bad unparsable dates
Message-ID: <455@focsys.UUCP>
Date: 29 May 89 14:38:05 GMT
References: <185@icdi10.UUCP> <730@dtscp1.UUCP>
Reply-To: larry@focsys.UUCP (Larry Williamson)
Organization: Focus Automation Systems, Waterloo, Ontario.
Lines: 21

In article <730@dtscp1.UUCP> scott@dtscp1.UUCP (Scott Barman) writes:
>
>>May 27 00:29	local	Unparsable date "31 Dec 69 23:59:59 GMT"
>
>Now for nearly a month, I have been getting mail that says this.
>
>Where do these come from?  Does the SysAdmin for the site producing
>these know about them?

I ran expire with verbose set to 3 and waded through >3 Meg of output
looking for the possible source of this annoying error. The files that
expire seemed to flag as the source of this error looked okay to me.

It looks as though the article is good, so why is expire complaining?
I could add more debugging info to expire to track it down, but maybe
someone else already has the answer?

-larry
-- 
Larry Williamson  -- Focus Systems -- Waterloo, Ontario
                  watmath!focsys!larry  (519) 746-4918