Path: utzoo!utgpu!water!watmath!clyde!rutgers!ucla-cs!zen!ucbvax!unisoft!mtxinu!ed
From: ed@mtxinu.UUCP (Ed Gould)
Newsgroups: news.software.b
Subject: Re: Expire "unparsable date" should tell me what article was botched
Message-ID: <537@mtxinu.UUCP>
Date: 17 Dec 87 23:02:18 GMT
References: <3258@tut.cis.ohio-state.edu>
Reply-To: ed@mtxinu.UUCP (Ed Gould)
Organization: mt Xinu, Berkeley
Lines: 18

>	expire: Unparsable date "31 Dec 69 23:59:59 GMT"
>
>We get one of these from Tut, the main departmental news server
>machine, and osu-cis, the 3B2 that does UUCP gatewaying for us.

We, too, were getting this message, after upgrading to parch 14.
I noticed it when the spool filesystem filled up, because expire
wasn't removing stuff.  Rebuilding the history file (expire -r)
solved the problem.

I agree, however, with the original request for more information
about the error as well.

-- 
Ed Gould                    mt Xinu, 2560 Ninth St., Berkeley, CA  94710  USA
{ucbvax,uunet}!mtxinu!ed    +1 415 644 0146

"`She's smart, for a woman, wonder how she got that way'..."