error in mysar-importer.php
when procedure stop by timeout she write in DB last
loaded time.
when we have 33 megabyte squid-log mysar sometimes
can't read line great or equal "last loaded time" and
then mysar-importer.php write incorrect last loaded
time.
on the next run mysar dublicate traffic.
Logged In: YES
user_id=614087
I used to update the timestamp after every record imported
in the database, but the performance penalty was
considerable, so I changed it to the current situation.
However, I did notice that on some errors the importer can
exit without updating the last record it processed, thus
leading to this bug.
The best would be to fix these unclean exits and put an
configurable option somewhere timestamp updates(per session
or per record).