expire: line too long
julien at trigofacile.com
Fri Aug 15 20:08:54 UTC 2008
> expire begin Fri Aug 15 04:07:40 CEST 2008: (-v3)
> expire: line too long /var/lib/news/history:586
> A look at the history file with "nl -ba /var/lib/news/history" indeed shows that line 1107 is broken.
But what is the 586th line?
> 1106 [8EA9B9694535F27DF09D9B537FF5D912] 1218726051~-~1218725167 @030342494733000000000050248A00000001@
> 1107 [1D7645EAFCB8FE0EC21AAE5F4AF165C4] 1218726051~1220021175~1218725175 @030342494733000000000050249100000001@
This line looks OK.
The date field consists of three sub-fields separated by a tilde. All
sub-fields are the text representation of the number of seconds since
the epoch -- i.e., a time_t; see gettimeofday(2). The first sub-field
is the article's arrival date. If copies of the article are still
present then the second sub-field is either the value of the article's
Expires header, or a hyphen if no expiration date was specified. If an
article has been expired then the second sub-field will be a hyphen.
The third sub-field is the value of the article's Date header, record-
ing when the article was posted.
« Et rose elle a vécu ce que vivent les roses :
L'espace d'un matin. » (François de Malherbe)
More information about the inn-workers