Yes, this happens because when the tally is ran directadmin issues a restart of the apache server so that the log files can be written to again.
Graceful restarting apache allows the server to restart without aborting current connections
With that being said... My question is this:
Is there a way to force directadmin to do a "graceful" restart and would that solve our problems? I would like to try this as my site is a pretty high traffic site and I dont want to deny customers a page if there is a way around it.
Thanks,
Curtis