🚀 go-pugleaf

Larry,

I got hosed by the regeneration this morning. Thankfully, none of my 7
clients are in the same fix. This had me goin' for a while, trying to
figure out what was what. Evidently, the logfile was written just as
one that I had already stored was made vulnerable.

I have cron that ran:
02 9 * * * cd public_html; gunzip -q httpd_access.0.gz
03 9 * * * cd public_html; ./webtrax.pl
05 9 * * * cd public_html; gzip -q httpd_access.0
just as the regenerationi took place.

WHile the file was in ungzipped state, the .tmp file was renamed and
overwrote what would have become .1.gz if things had gone normally.
The result is that I lost the file from Oct 5.

There is a .0.gz (Oct. 6 data) and a .2.gz (Oct. 4 data)
but .1.gz is missing. 

What are the odds of that? Can this be regenerated for user bjspace
on shell3, please? Thanks for whatever you can do.

Also noted: at 13:30 three of my other accounts are still sitting at
.tmp stage, not converting to .0 names. should I just wait on those?

bjspace@best.com
--
    B.E.Johnson             Space: To go and learn is reason enough!
    bj@imperialearth.com
    http://www.imperialearth.com/