bob@omni.com (Bob Weissman) (09/29/90)
Does anyone have a fix for this problem where expire fails to log the offending file name when it can't parse a date? Our logs are chock full of lines like the ones below, and I can't seem to find any files containing the unparsable date strings. expire: : Unparsable date "184475170" expire: : Unparsable date "184475216" expire: : Unparsable date "184482218" expire: : Unparsable date "184482219" expire: : Unparsable date "184482220" The second colon in these messages should be preceded by a file name; this indicates the global string "filename" is empty. Does expire unlink the offending articles, rendering this a non-issue? Or do I need to worry about it? Thanks, -- Bob Weissman Internet: bob@omni.com UUCP: ...!{apple,decwrl,pyramid,sgi,uunet}!omni!bob