Why not use EnableLockForUpdate option (works too for multiple site configurations)? This option is in upstream from 5.0 release and seems to be a simplest solution of the original problem.
Documentation: http://awstats.sourceforge.net/docs/awstats_config.html#EnableLockForUpdate If other developers would agree, I'll set the severity of this bug to wishlist and retitle one accordingly (awstats cron wrapper). -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
