Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ll-xn!mit-eddie!husc6!psuvax1!vu-vlsi!devon!paul
From: paul@devon.UUCP (Paul Sutcliffe Jr.)
Newsgroups: news.software.b
Subject: Problem with expire (patchlevel 11)
Message-ID: <487@devon.UUCP>
Date: Tue, 3-Nov-87 15:21:33 EST
Article-I.D.: devon.487
Posted: Tue Nov  3 15:21:33 1987
Date-Received: Sat, 7-Nov-87 08:31:42 EST
Organization: Devon Computer Services, Allentown, PA
Lines: 29
Keywords: expire, bug, problem

I recently installed patches 9, 10 and 11 in my news software.  Since
that time, I have been getting the following error message from expire
during its nightly run (from cron):

    expire: Unparsable date "31 Dec 69 23:59:59 GMT"

I get several of these each run.  They are from the std{out,err} of
the cron process.  At the same time, I get messages like these:

    Nov  3 00:59	news	expire: Unparsable date "31 Dec 69 23:59:59 GMT"

in LIBDIR/log and LIBDIR/errlog.

My guess is that since Un*x keeps its time in a long, with 0L
representing "1 Jan 70 00:00:00 GMT", that the above message comes
from trying to handle a "-1" value.

If this matters, I am running B-news 2.11 patchlevel 11 on a Tandy
Model 16; Tandy Xenix 3.1.2; with OSTYPE=v7 in the Makefile.  I have
verified that the same problem exists at my news-neighbor (vu-vlsi) on
a Pyramid 90x; OSx 4.0; with news running in the BSD universe.

- paul

-- 
Paul Sutcliffe, Jr.

UUCP (smart):  paul@devon.UUCP
UUCP (dumb):   ...{rutgers,ihnp4,cbosgd}!bpa!vu-vlsi!devon!paul