Xref: utzoo news.admin:8124 news.software.b:3989 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!spdcc!gst From: gst@spdcc.COM (Gary Trujillo) Newsgroups: news.admin,news.software.b Subject: Re: "Unparseable date" error from expire Summary: Funny you should mention it! Message-ID: <1314@ursa-major.SPDCC.COM> Date: 20 Jan 90 14:56:38 GMT References: <1556@fallst.UUCP> Reply-To: gst@ursa-major.spdcc.COM (Gary S. Trujillo) Lines: 489 In article <1556@fallst.UUCP> tkevans@fallst.UUCP (Tim Evans) writes: > I've been seeing a bunch of error messages like the following in my > news errlog lately... > > Jan 5 22:10 news expire: : Unparsable date "11/25/89 05:20 \ > comp.mail.misc/1518 comp.mail.uucp/2343 comp.unix.questions/10123 \ > comp.mail.sendmail/1102 new<18556@watdragon.waterloo.edu> \ > 11/25/89 05:23" Well, I was just about to post the following article when I spotted Tim's. Since my problem differes from his only in that I don't get a list of actual news articles, I thought I'd post my report as a followup... For the past several months, I have been getting messages from expire every time I run it (I do it by hand, due to the fact that I get few newsgroups, and am the only real user on my machine). Said messages are of the form: expire: : Unparsable date "595973992" expire: : Unparsable date "595974046" expire: : Unparsable date "595974046" I'm not sure exactly when it all began, as I hadn't run expire in a few weeks, as I recall, when I first saw these error messages, though I think it might have been shortly after I installed a new version of news. (I'm running B news 2.11 at patch level 18.) I finally got tired of seeing these messages every time I run expire, and decided to do a little sleuthing. I just grepped for the numbers in these messages in the files in /usr/lib/news/history.d, and came up with the following list, which I've sorted and prettified a bit: file line 9 8 <59@gnosys.UUCP> 595974127 hbe/1 9 9 <59@gnosys.UUCP> 595974127 0 6 <60@gnosys.UUCP> 595974046 hbe/2 0 7 <60@gnosys.UUCP> 595974046 1 9 <61@gnosys.UUCP> 595974058 hbe/3 1 10 <61@gnosys.UUCP> 595974058 3 11 <63@gnosys.UUCP> 595974079 hbe/4 6 7 <66@gnosys.UUCP> 595974090 hbe/6 6 8 <66@gnosys.UUCP> 595974090 7 12 <67@gnosys.UUCP> 591024835 hbe/7 8 10 <68@gnosys.UUCP> 595974106 hbe/8 8 11 <68@gnosys.UUCP> 595974106 9 7 <69@gnosys.UUCP> 595974116 hbe/9 6 6 <76@gnosys.UUCP> 595974012 hbe/10 7 11 <77@gnosys.UUCP> 595974029 hbe/11 9 16 <79@gnosys.UUCP> 596098480 hbe/12 0 4 <80@gnosys.UUCP> 595973992 hbe/13 4 10 <84@gnosys.UUCP> 596915433 hbe/14 8 8 <88@gnosys.UUCP> 598032793 hbe/15 3 18 <93@gnosys.UUCP> 598209739 hbe/16 4 16 <94@gnosys.UUCP> 598399278 hbe/17 6 17 <96@gnosys.UUCP> 599499696 hbe/18 7 1 <97@gnosys.UUCP> 599500152 hbe/19 Since there are articles beyond #19 in local newsgroup "hbe" (which I've deliberately never expired), I decided to look at files 19 & 20, to see if there was any interesting difference between the two. There is, in fact: 19:Date: 30 Dec 88 15:49:10 GMT 20:Date: 16 Jan 89 20:34:45 GMT Article 19 was the last one posted in 1988, and 20 was the first posted in 1989. Hmmmmm.... Any thoughts?? I don't care enough about the problem to actually dig out the code and pore through it, but I thought someone out there who does might want to check it out. Please let me know via email (I don't read this newsgroup regularly) if you come up with anything. Thanks! -- Gary S. Trujillo gst@gnosys.svle.ma.us Somerville, Massachusetts {wjh12,spdcc,ima,cdp}!gnosys!gst Newsgroups: poster Subject: Re: "Unparseable date" error from expire Summary: Funny you should mention it! References: <1556@fallst.UUCP> Reply-To: gst@ursa-major.spdcc.COM (Gary S. Trujillo) In article <1556@fallst.UUCP> tkevans@fallst.UUCP (Tim Evans) writes: > I've been seeing a bunch of error messages like the following in my > news errlog lately... > > Jan 5 22:10 news expire: : Unparsable date "11/25/89 05:20 \ > comp.mail.misc/1518 comp.mail.uucp/2343 comp.unix.questions/10123 \ > comp.mail.sendmail/1102 new<18556@watdragon.waterloo.edu> \ > 11/25/89 05:23" Well, I was just about to post the following article when I spotted Tim's. Since my problem differes from his only in that I don't get a list of actual news articles, I thought I'd post my report as a followup... For the past several months, I have been getting messages from expire every time I run it (I do it by hand, due to the fact that I get few newsgroups, and am the only real user on my machine). Said messages are of the form: expire: : Unparsable date "595973992" expire: : Unparsable date "595974046" expire: : Unparsable date "595974046" I'm not sure exactly when it all began, as I hadn't run expire in a few weeks, as I recall, when I first saw these error messages, though I think it might have been shortly after I installed a new version of news. (I'm running B news 2.11 at patch level 18.) I finally got tired of seeing these messages every time I run expire, and decided to do a little sleuthing. I just grepped for the numbers in these messages in the files in /usr/lib/news/history.d, and came up with the following list, which I've sorted and prettified a bit: file line 9 8 <59@gnosys.UUCP> 595974127 hbe/1 9 9 <59@gnosys.UUCP> 595974127 0 6 <60@gnosys.UUCP> 595974046 hbe/2 0 7 <60@gnosys.UUCP> 595974046 1 9 <61@gnosys.UUCP> 595974058 hbe/3 1 10 <61@gnosys.UUCP> 595974058 3 11 <63@gnosys.UUCP> 595974079 hbe/4 6 7 <66@gnosys.UUCP> 595974090 hbe/6 6 8 <66@gnosys.UUCP> 595974090 7 12 <67@gnosys.UUCP> 591024835 hbe/7 8 10 <68@gnosys.UUCP> 595974106 hbe/8 8 11 <68@gnosys.UUCP> 595974106 9 7 <69@gnosys.UUCP> 595974116 hbe/9 6 6 <76@gnosys.UUCP> 595974012 hbe/10 7 11 <77@gnosys.UUCP> 595974029 hbe/11 9 16 <79@gnosys.UUCP> 596098480 hbe/12 0 4 <80@gnosys.UUCP> 595973992 hbe/13 4 10 <84@gnosys.UUCP> 596915433 hbe/14 8 8 <88@gnosys.UUCP> 598032793 hbe/15 3 18 <93@gnosys.UUCP> 598209739 hbe/16 4 16 <94@gnosys.UUCP> 598399278 hbe/17 6 17 <96@gnosys.UUCP> 599499696 hbe/18 7 1 <97@gnosys.UUCP> 599500152 hbe/19 Since there are articles beyond #19 in local newsgroup "hbe" (which I've deliberately never expired), I decided to look at files 19 & 20, to see if there was any interesting difference between the two. There is, in fact: 19:Date: 30 Dec 88 15:49:10 GMT 20:Date: 16 Jan 89 20:34:45 GMT Article 19 was the last one posted in 1988, and 20 was the first posted in 1989. Hmmmmm.... Any thoughts?? I don't care enough about the problem to actually dig out the code and pore through it, but I thought someone out there who does might want to check it out. Please let me know via email (I don't read this newsgroup regularly) if you come up with anything. Thanks! ----- News saved at 20 Jan 90 14:54:29 GMT In article <1556@fallst.UUCP> tkevans@fallst.UUCP (Tim Evans) writes: > I've been seeing a bunch of error messages like the following in my > news errlog lately... > > Jan 5 22:10 news expire: : Unparsable date "11/25/89 05:20 \ > comp.mail.misc/1518 comp.mail.uucp/2343 comp.unix.questions/10123 \ > comp.mail.sendmail/1102 new<18556@watdragon.waterloo.edu> \ > 11/25/89 05:23" Well, I was just about to post the following article when I spotted Tim's. Since my problem differes from his only in that I don't get a list of actual news articles, I thought I'd post my report as a followup... For the past several months, I have been getting messages from expire every time I run it (I do it by hand, due to the fact that I get few newsgroups, and am the only real user on my machine). Said messages are of the form: expire: : Unparsable date "595973992" expire: : Unparsable date "595974046" expire: : Unparsable date "595974046" I'm not sure exactly when it all began, as I hadn't run expire in a few weeks, as I recall, when I first saw these error messages, though I think it might have been shortly after I installed a new version of news. (I'm running B news 2.11 at patch level 18.) I finally got tired of seeing these messages every time I run expire, and decided to do a little sleuthing. I just grepped for the numbers in these messages in the files in /usr/lib/news/history.d, and came up with the following list, which I've sorted and prettified a bit: file line 9 8 <59@gnosys.UUCP> 595974127 hbe/1 9 9 <59@gnosys.UUCP> 595974127 0 6 <60@gnosys.UUCP> 595974046 hbe/2 0 7 <60@gnosys.UUCP> 595974046 1 9 <61@gnosys.UUCP> 595974058 hbe/3 1 10 <61@gnosys.UUCP> 595974058 3 11 <63@gnosys.UUCP> 595974079 hbe/4 6 7 <66@gnosys.UUCP> 595974090 hbe/6 6 8 <66@gnosys.UUCP> 595974090 7 12 <67@gnosys.UUCP> 591024835 hbe/7 8 10 <68@gnosys.UUCP> 595974106 hbe/8 8 11 <68@gnosys.UUCP> 595974106 9 7 <69@gnosys.UUCP> 595974116 hbe/9 6 6 <76@gnosys.UUCP> 595974012 hbe/10 7 11 <77@gnosys.UUCP> 595974029 hbe/11 9 16 <79@gnosys.UUCP> 596098480 hbe/12 0 4 <80@gnosys.UUCP> 595973992 hbe/13 4 10 <84@gnosys.UUCP> 596915433 hbe/14 8 8 <88@gnosys.UUCP> 598032793 hbe/15 3 18 <93@gnosys.UUCP> 598209739 hbe/16 4 16 <94@gnosys.UUCP> 598399278 hbe/17 6 17 <96@gnosys.UUCP> 599499696 hbe/18 7 1 <97@gnosys.UUCP> 599500152 hbe/19 Since there are articles beyond #19 in local newsgroup "hbe" (which I've deliberately never expired), I decided to look at files 19 & 20, to see if there was any interesting difference between the two. There is, in fact: 19:Date: 30 Dec 88 15:49:10 GMT 20:Date: 16 Jan 89 20:34:45 GMT Article 19 was the last one posted in 1988, and 20 was the first posted in 1989. Hmmmmm.... Any thoughts?? I don't care enough about the problem to actually dig out the code and pore through it, but I thought someone out there who does might want to check it out. Please let me know via email (I don't read this newsgroup regularly) if you come up with anything. Thanks! -- Gary S. Trujillo gst@gnosys.svle.ma.us Somerville, Massachusetts {wjh12,spdcc,ima,cdp}!gnosys!gst Newsgroups: poster Subject: Re: "Unparseable date" error from expire Summary: Funny you should mention it! References: <1556@fallst.UUCP> Reply-To: gst@ursa-major.spdcc.COM (Gary S. Trujillo) In article <1556@fallst.UUCP> tkevans@fallst.UUCP (Tim Evans) writes: > I've been seeing a bunch of error messages like the following in my > news errlog lately... > > Jan 5 22:10 news expire: : Unparsable date "11/25/89 05:20 \ > comp.mail.misc/1518 comp.mail.uucp/2343 comp.unix.questions/10123 \ > comp.mail.sendmail/1102 new<18556@watdragon.waterloo.edu> \ > 11/25/89 05:23" Well, I was just about to post the following article when I spotted Tim's. Since my problem differes from his only in that I don't get a list of actual news articles, I thought I'd post my report as a followup... For the past several months, I have been getting messages from expire every time I run it (I do it by hand, due to the fact that I get few newsgroups, and am the only real user on my machine). Said messages are of the form: expire: : Unparsable date "595973992" expire: : Unparsable date "595974046" expire: : Unparsable date "595974046" I'm not sure exactly when it all began, as I hadn't run expire in a few weeks, as I recall, when I first saw these error messages, though I think it might have been shortly after I installed a new version of news. (I'm running B news 2.11 at patch level 18.) I finally got tired of seeing these messages every time I run expire, and decided to do a little sleuthing. I just grepped for the numbers in these messages in the files in /usr/lib/news/history.d, and came up with the following list, which I've sorted and prettified a bit: file line 9 8 <59@gnosys.UUCP> 595974127 hbe/1 9 9 <59@gnosys.UUCP> 595974127 0 6 <60@gnosys.UUCP> 595974046 hbe/2 0 7 <60@gnosys.UUCP> 595974046 1 9 <61@gnosys.UUCP> 595974058 hbe/3 1 10 <61@gnosys.UUCP> 595974058 3 11 <63@gnosys.UUCP> 595974079 hbe/4 6 7 <66@gnosys.UUCP> 595974090 hbe/6 6 8 <66@gnosys.UUCP> 595974090 7 12 <67@gnosys.UUCP> 591024835 hbe/7 8 10 <68@gnosys.UUCP> 595974106 hbe/8 8 11 <68@gnosys.UUCP> 595974106 9 7 <69@gnosys.UUCP> 595974116 hbe/9 6 6 <76@gnosys.UUCP> 595974012 hbe/10 7 11 <77@gnosys.UUCP> 595974029 hbe/11 9 16 <79@gnosys.UUCP> 596098480 hbe/12 0 4 <80@gnosys.UUCP> 595973992 hbe/13 4 10 <84@gnosys.UUCP> 596915433 hbe/14 8 8 <88@gnosys.UUCP> 598032793 hbe/15 3 18 <93@gnosys.UUCP> 598209739 hbe/16 4 16 <94@gnosys.UUCP> 598399278 hbe/17 6 17 <96@gnosys.UUCP> 599499696 hbe/18 7 1 <97@gnosys.UUCP> 599500152 hbe/19 Since there are articles beyond #19 in local newsgroup "hbe" (which I've deliberately never expired), I decided to look at files 19 & 20, to see if there was any interesting difference between the two. There is, in fact: 19:Date: 30 Dec 88 15:49:10 GMT 20:Date: 16 Jan 89 20:34:45 GMT Article 19 was the last one posted in 1988, and 20 was the first posted in 1989. Hmmmmm.... Any thoughts?? I don't care enough about the problem to actually dig out the code and pore through it, but I thought someone out there who does might want to check it out. Please let me know via email (I don't read this newsgroup regularly) if you come up with anything. Thanks! -- Gary S. Trujillo gst@gnosys.svle.ma.us Somerville, Massachusetts {wjh12,spdcc,ima,cdp}!gnosys!gst Subject: Re: "Unparseable date" error from expire Summary: Funny you should mention it! References: <1556@fallst.UUCP> Reply-To: gst@ursa-major.spdcc.COM (Gary S. Trujillo) In article <1556@fallst.UUCP> tkevans@fallst.UUCP (Tim Evans) writes: > I've been seeing a bunch of error messages like the following in my > news errlog lately... > > Jan 5 22:10 news expire: : Unparsable date "11/25/89 05:20 \ > comp.mail.misc/1518 comp.mail.uucp/2343 comp.unix.questions/10123 \ > comp.mail.sendmail/1102 new<18556@watdragon.waterloo.edu> \ > 11/25/89 05:23" Well, I was just about to post the following article when I spotted Tim's. Since my problem differes from his only in that I don't get a list of actual news articles, I thought I'd post my report as a followup... For the past several months, I have been getting messages from expire every time I run it (I do it by hand, due to the fact that I get few newsgroups, and am the only real user on my machine). Said messages are of the form: expire: : Unparsable date "595973992" expire: : Unparsable date "595974046" expire: : Unparsable date "595974046" I'm not sure exactly when it all began, as I hadn't run expire in a few weeks, as I recall, when I first saw these error messages, though I think it might have been shortly after I installed a new version of news. (I'm running B news 2.11 at patch level 18.) I finally got tired of seeing these messages every time I run expire, and decided to do a little sleuthing. I just grepped for the numbers in these messages in the files in /usr/lib/news/history.d, and came up with the following list, which I've sorted and prettified a bit: file line 9 8 <59@gnosys.UUCP> 595974127 hbe/1 9 9 <59@gnosys.UUCP> 595974127 0 6 <60@gnosys.UUCP> 595974046 hbe/2 0 7 <60@gnosys.UUCP> 595974046 1 9 <61@gnosys.UUCP> 595974058 hbe/3 1 10 <61@gnosys.UUCP> 595974058 3 11 <63@gnosys.UUCP> 595974079 hbe/4 6 7 <66@gnosys.UUCP> 595974090 hbe/6 6 8 <66@gnosys.UUCP> 595974090 7 12 <67@gnosys.UUCP> 591024835 hbe/7 8 10 <68@gnosys.UUCP> 595974106 hbe/8 8 11 <68@gnosys.UUCP> 595974106 9 7 <69@gnosys.UUCP> 595974116 hbe/9 6 6 <76@gnosys.UUCP> 595974012 hbe/10 7 11 <77@gnosys.UUCP> 595974029 hbe/11 9 16 <79@gnosys.UUCP> 596098480 hbe/12 0 4 <80@gnosys.UUCP> 595973992 hbe/13 4 10 <84@gnosys.UUCP> 596915433 hbe/14 8 8 <88@gnosys.UUCP> 598032793 hbe/15 3 18 <93@gnosys.UUCP> 598209739 hbe/16 4 16 <94@gnosys.UUCP> 598399278 hbe/17 6 17 <96@gnosys.UUCP> 599499696 hbe/18 7 1 <97@gnosys.UUCP> 599500152 hbe/19 Since there are articles beyond #19 in local newsgroup "hbe" (which I've deliberately never expired), I decided to look at files 19 & 20, to see if there was any interesting difference between the two. There is, in fact: 19:Date: 30 Dec 88 15:49:10 GMT 20:Date: 16 Jan 89 20:34:45 GMT Article 19 was the last one posted in 1988, and 20 was the first posted in 1989. Hmmmmm.... Any thoughts?? I don't care enough about the problem to actually dig out the code and pore through it, but I thought someone out there who does might want to check it out. Please let me know via email (I don't read this newsgroup regularly) if you come up with anything. Thanks! -- Gary S. Trujillo gst@gnosys.svle.ma.us Somerville, Massachusetts {wjh12,spdcc,ima,cdp}!gnosys!gst Newsgroups: poster Subject: Re: "Unparseable date" error from expire Summary: Funny you should mention it! References: <1556@fallst.UUCP> Reply-To: gst@ursa-major.spdcc.COM (Gary S. Trujillo) In article <1556@fallst.UUCP> tkevans@fallst.UUCP (Tim Evans) writes: > I've been seeing a bunch of error messages like the following in my > news errlog lately... > > Jan 5 22:10 news expire: : Unparsable date "11/25/89 05:20 \ > comp.mail.misc/1518 comp.mail.uucp/2343 comp.unix.questions/10123 \ > comp.mail.sendmail/1102 new<18556@watdragon.waterloo.edu> \ > 11/25/89 05:23" Well, I was just about to post the following article when I spotted Tim's. Since my problem differes from his only in that I don't get a list of actual news articles, I thought I'd post my report as a followup... For the past several months, I have been getting messages from expire every time I run it (I do it by hand, due to the fact that I get few newsgroups, and am the only real user on my machine). Said messages are of the form: expire: : Unparsable date "595973992" expire: : Unparsable date "595974046" expire: : Unparsable date "595974046" I'm not sure exactly when it all began, as I hadn't run expire in a few weeks, as I recall, when I first saw these error messages, though I think it might have been shortly after I installed a new version of news. (I'm running B news 2.11 at patch level 18.) I finally got tired of seeing these messages every time I run expire, and decided to do a little sleuthing. I just grepped for the numbers in these messages in the files in /usr/lib/news/history.d, and came up with the following list, which I've sorted and prettified a bit: file line 9 8 <59@gnosys.UUCP> 595974127 hbe/1 9 9 <59@gnosys.UUCP> 595974127 0 6 <60@gnosys.UUCP> 595974046 hbe/2 0 7 <60@gnosys.UUCP> 595974046 1 9 <61@gnosys.UUCP> 595974058 hbe/3 1 10 <61@gnosys.UUCP> 595974058 3 11 <63@gnosys.UUCP> 595974079 hbe/4 6 7 <66@gnosys.UUCP> 595974090 hbe/6 6 8 <66@gnosys.UUCP> 595974090 7 12 <67@gnosys.UUCP> 591024835 hbe/7 8 10 <68@gnosys.UUCP> 595974106 hbe/8 8 11 <68@gnosys.UUCP> 595974106 9 7 <69@gnosys.UUCP> 595974116 hbe/9 6 6 <76@gnosys.UUCP> 595974012 hbe/10 7 11 <77@gnosys.UUCP> 595974029 hbe/11 9 16 <79@gnosys.UUCP> 596098480 hbe/12 0 4 <80@gnosys.UUCP> 595973992 hbe/13 4 10 <84@gnosys.UUCP> 596915433 hbe/14 8 8 <88@gnosys.UUCP> 598032793 hbe/15 3 18 <93@gnosys.UUCP> 598209739 hbe/16 4 16 <94@gnosys.UUCP> 598399278 hbe/17 6 17 <96@gnosys.UUCP> 599499696 hbe/18 7 1 <97@gnosys.UUCP> 599500152 hbe/19 Since there are articles beyond #19 in local newsgroup "hbe" (which I've deliberately never expired), I decided to look at files 19 & 20, to see if there was any interesting difference between the two. There is, in fact: 19:Date: 30 Dec 88 15:49:10 GMT 20:Date: 16 Jan 89 20:34:45 GMT Article 19 was the last one posted in 1988, and 20 was the first posted in 1989. Hmmmmm.... Any thoughts?? I don't care enough about the problem to actually dig out the code and pore through it, but I thought someone out there who does might want to check it out. Please let me know via email (I don't read this newsgroup regularly) if you come up with anything. Thanks! -- Gary S. Trujillo gst@gnosys.svle.ma.us Somerville, Massachusetts {wjh12,spdcc,ima,cdp}!gnosys!gst