cstdenis - 2011-06-02

I have an awstats process that has been running for over 10 hours. Now that
it's no longer night, leaving it running is starting to be a significant
performance problem. However due to awstats current design, there is no way
for me to end it without loosing all progress made in those 10 hours which is
a real waste.

Awstats should stop after processing the current log line, delete processed
lines from the log file (if configured to do so) and write it's stats to disk
before exiting when receiving a signal like this. Additionally, it would be
useful to have another signal like USR1 or maybe HUP that causes it to take
this action without exiting.