Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!tank!mimsy!dftsrv!ames!amdcad!sun!pitstop!sundc!seismo!uunet!csdev!ll1a!nesac2!jec
From: jec@nesac2.UUCP (John Carter ATLN SADM)
Newsgroups: news.software.b
Subject: Re: Problem with expire
Summary: read the date again
Keywords: expire
Message-ID: <1286@nesac2.UUCP>
Date: 22 Oct 88 21:06:40 GMT
References: <542@dms.UUCP> <9617@umn-cs.CS.UMN.EDU>
Organization: A.T.&T. Lisle, Ill.
Lines: 31

In article <9617@umn-cs.CS.UMN.EDU>, wytten@umn-cs.CS.UMN.EDU (Dale R. Wyttenbach) writes:
> In article <542@dms.UUCP> morris@dms.UUCP (Jim Morris) writes:
] ]
] ]Can anyone tell me why I get the following error message fairly frequently:
] ]
] ]	expire: Unparsable date "31 Dec 69 23:59:59 GMT"
] ]
] ]when expire runs.
] 
] I have this problem, too, and I never saw a response to this posting.
] 
] We recently went from a VAX 11/780 and 4.3 BSD to a Sequent S27 and DYNIX
] 3.0.12.  I don't remember if I was having the '31 Dec 69' problem on the
] VAX.  
] 
] umn-cs is running 2.11 news, albeit sort of lamely right now.
]	{deletions}
] Dale Wyttenbach
] {wytten,news}@umn-cs.cs.umn.edu
] ...rutgers!umn-cs!wytten

UNIX(tm) was 'born' 1/1/1970 - a date of 12/31/1969 23:59 says that the
call to get the time returned a -1, and that the call does no error checks.

Sounds like a bug in the time code - int/long, 16/32/64 bits, big-endian vs.
little-endian, whatever else you can think of that might break what you
should get as time_t.
-- 
USnail: John Carter, AT&T, 401 W. Peachtree, FLOC 2932-6, Atlanta GA 30308
Video:	...att!nesac2!jec    Voice: 404+581-6239
The machine belongs to the company.  The opinions are mine.