Hourly PrimeNet Reports archived again!
 

Hello everyone, the hourly PrimeNet Reports are being archived once again.
The summary.txt, status.txt, and cleared.txt are automatically grabbed at 20, 25, and 35 minutes after the hour respectively. Archived using bzip2 and posted for everyone.

Check it out here:
[url]http://www.mersenneforum.org/primenet[/url]

Yay!

:bow:

The current hours' reports are now on there 'decompressed' in their respective folders. This is probably more useful for viewing the summary.txt since it's small, but the status.txt and cleared.txt are huge.

Great service, thanks!
Windows users may perhaps also consider the LGPLed GUI-tool [URL=http://www.7-zip.org/]7-ZIP[/URL] to extract the bzip2-archives.

Slight issue. Summary.txt, at least for the current hour, is a bit truncated:

[CODE] 23000000 23099999 13 106 1123 840
23100000 23199999 14 155 1289 866 2
23200000 23299999 10 231 1307 889
23300000 23399999 15 283 1394 771 1
23400000 23499999 12 192 1485 703
23500000 23599999 30 267 1477 698 1
23600000 23699999 34 237 1414 760
23700000 23799999 31 293 1473 666 1
23800000 [/CODE]

You got more than I. Liklely server loading. Get hit all over the place with the M41.txt etc.

No, no, the report on mersenne.org is fine, the copy that's in the archive is truncated. Don't know about the others, I'm too tired right now to check. :yawn:

Still, caused by a loading issue. at time of archive capture, too busy.

Yes, that tends to happen at times, it is probably (as noted earlier) server load issues. This was one reason to try to mirror the current files. The current files are mirrored from the site just after they are made available on Primenet. However, the files are grabbed again towards the end of the hour for archiving.

It turned out that the summary.txt file was being mirrored from the Primenet server at the time that file was being generated, so it only got what it had up to that point. It now gets it just a couple minutes later to give it enough time to finish.

The current hourly files are also at the site already gzipped. The server has on-the-fly gzip compression of text files, but if a gziped file already exists, it sends that one instead, thu saving work for the server. Most web browsers have build in gzip decompression built in, so you should be able to see the gzipped version in your browser.
The archived files are still bzip2 compressed due to better compression ratios.
Check it out here:
[url]http://www.mersenneforum.org/primenet[/url]