bob@omni.com (Bob Weissman) (10/12/90)
I have been getting *hundreds* of these messages every night from
expire. Can anyone tell me what they mean and how to get rid of them?
The lone colon in the message indicates the global char array
"filename" contains an empty string, making it difficult to track down
the source of these errors.
I did a "find" piped into "grep" looking for these strings and
am reasonably certain they don't actually occur inside any news
articles. Is this a date format anyone recognizes?
This is news version B 2.11.19 10/30/89 on a Sun 4/280 under SunOS
4.0.3, if that matters.
Oct 11 03:53 news expire: : Unparsable date "184482407"
Oct 11 03:53 news expire: : Unparsable date "184482408"
Oct 11 03:53 news expire: : Unparsable date "184482409"
Oct 11 03:53 news expire: : Unparsable date "184482411"
Oct 11 03:53 news expire: : Unparsable date "184482412"
Oct 11 03:53 news expire: : Unparsable date "184482414"
Oct 11 03:53 news expire: : Unparsable date "184482415"
Oct 11 03:53 news expire: : Unparsable date "184482416"
Oct 11 03:53 news expire: : Unparsable date "184482416"
Oct 11 03:53 news expire: : Unparsable date "184482417"
Oct 11 03:53 news expire: : Unparsable date "184482418"
Oct 11 03:53 news expire: : Unparsable date "184482418"
Oct 11 03:53 news expire: : Unparsable date "184482419"
Oct 11 03:53 news expire: : Unparsable date "184482420"
Oct 11 03:53 news expire: : Unparsable date "184482420"
Thanks,
--
Bob Weissman
Internet: bob@omni.com
UUCP: ...!{apple,decwrl,pyramid,sgi,uunet}!omni!bob