> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-1-822176994@cynjut.neonramp.com>
> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-2-822176994@cynjut.neonramp.com>
> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-3-822176994@cynjut.neonramp.com>
> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-4-822176994@cynjut.neonramp.com>
> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-5-822176994@cynjut.neonramp.com>
> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-6-822176994@cynjut.neonramp.com>
> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-7-822176994@cynjut.neonramp.com>
> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-8-822176994@cynjut.neonramp.com>
> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-9-822176994@cynjut.neonramp.com>
> histtrim: bad expiry date '02/07/96 16:29:54 CDT' in <386bsd-faq-10-82217699@cynjut.neonramp.com>
The approval process should check for this, IMHO. Even some versions of
auto-faq seem to generate somewhat bogus dates. The effect is that these
articles are expired as usual, which mostly is shorter than their intended
lifetime.
(I've even found articles in news.answers that had neither Expires nor
Supersededs lines, which by the default setup of dexpire means they are
_never_ expired, but that's another problem yet...)
olaf
--
___ Olaf.Titz@inka.de or @{stud,informatik}.uni-karlsruhe.de ____
__ o <URL:http://www.inka.de/~bigred/> <IRC:praetorius>
__/<_ >> Just as long as the wheels keep on turning round
_)>(_)______________ I will live for the groove 'til the sun goes down << ____
[
Usenet Hypertext FAQ Archive |
Search Mail Archive |
Authors |
Usenet
]
[
1993 |
1994 |
1995 |
1996 |
1997
]
© Copyright The Landfield Group, 1997
All rights reserved