Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!ukc!stl!dww From: dww@stl.stc.co.uk (David Wright) Newsgroups: news.admin Subject: Re: question on bad newsgroups Keywords: nomatch Message-ID: <1487@stl.stc.co.uk> Date: 1 Jun 89 08:43:48 GMT References: <185@icdi10.uucp> <730@dtscp1.uucp> <805@ivucsb.sba.ca.us> <200@icdi10.UUCP> Sender: news@stl.stc.co.uk Reply-To: "David Wright" Organization: STC Technology Limited, London Road, Harlow, Essex, UK Lines: 23 In article <200@icdi10.UUCP> fr@icdi10.UUCP (Fred Rump from home) writes: #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? #> #> ... 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. #And yes this is Xenix (386) 2.3.2 Just to confirm it's not a local problem - we get it too, on a Sun3 (SunOS 3.5). So it's not just a Xenix problem. I can only assume that expire is choking over something in the history file. As our history file is currently 3.5MBytes, I haven't found what. Regards, "None shall be enslaved by poverty, ignorance or conformity" David Wright STL, London Road, Harlow, Essex CM17 9NA, UK dww@stl.stc.co.uk ...uunet!mcvax!ukc!stl!dww PSI%234237100122::DWW