I am surprised to find out that cpanel's log system is one of the worst. The thing is, if they want to customize their own log files (ie. domlogs), then they pretty darn sure have to customize the logrotation for it as well. Instead, they had this logs to delete after each statistic software update which is a lame approach of handling the logs. On top of that, they don't even customize their own logs to use logrotate...that's pretty pathetic. No wonder urchin doesn't work well with cpanel. Here is what I did with urchin, 1) install it in a directory with different name than "urchin" so that WHM/cpanel does not recognize it as urchin and start adding it into cpanel. 2) add another customlog line in my httpd.conf. This means, my domains will be running 2 customlogs. One for the normal webalizer/analog/awstats and another for urchin. 3) store this log file in /usr/local/apache/logs 4) follow this howto to fix cpanel's log problems : http://www.webhostgear.com/144.html 5) create the profile in urchin. Now, users will have to login to urchin to see their stats instead of going to cpanel. This is my preferred method and these people agrees (http://forum.ev1servers.net/showthread.php?t=51541&highlight=cpanel+urchin). Now...my question, is there any better way to deal with domlogs? I read that someone is using cronolog (http://forum.ev1servers.net/showthread.php?t=51541&highlight=cronolog) for those urchin logs. Will this program reduce my apache load of having to log into 2 log files? Thanks in advance.