Xref: utzoo news.sysadmin:2432 news.admin:5835 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!cdin-1!icdi10!fr From: fr@icdi10.UUCP (Fred Rump from home) Newsgroups: news.sysadmin,news.admin Subject: Re: question on bad newsgroups Keywords: nomatch Message-ID: <200@icdi10.UUCP> Date: 30 May 89 13:42:42 GMT References: <185@icdi10.uucp> <730@dtscp1.uucp> <805@ivucsb.sba.ca.us> Reply-To: fr@icdi10.UUCP (Fred Rump from home) Organization: From Home but normally @ Compudata Inc. Phila PA Lines: 32 Summary: Expires: Sender: Followup-To: Distribution: In article <805@ivucsb.sba.ca.us> news@ivucsb.UUCP (Todd Day) writes: >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" >~Where do these come from? > >I'm not sure, but here's my theory. Someone's machine (probably a >Xenix system :-) is returning -1 from the time(2) function. There >is probably no error checking done by inews (who would ever suspect >that time(2) would return with an error?), and it passes this to >ctime(3c). ctime(3c) does no error checking, either, and faithfully >converts the -1 to one second before the UNIX big-bang. >Actually, since your logfile says "local", maybe it is YOUR machine >that is producing the bogus date! I have no doubt that it is. But it's doing the same thing on a bunch of other machines too. So it's not unique to the world and must be something that is fixable. But how? And yes this is Xenix (386) 2.3.2 Maybe it'll just go away? It's not been around since I asked about it. Like magic I gave away it's secret and it went into blissful sleep somewhere in the past before the last second of 1969? Fred icdi10!fr@cdin-1.uu.net -- This is my house. My castle will get started right after I finish with news. 26 Warren St. ...{dsinc bpa uunet}!cdin-1!icdi10!fr Beverly, NJ 08010 or INTERNET: fred@cdin-1.uu.net or icdi10!fr@icdi10.uu.net 609-386-6846 "Freude... Alle Menschen werden Brueder..." - Schiller