CPX uses savelogs to do its own log rotation. So if you use CPX (and
savelogs), you'll want to disable the log rotation in Urchin. When you
specify the log source in urchin, you should append a '*' at the end so it
will include all the rotated logs as well. For example:
/www/logs/USER/access_log*
Urchin 5 is smart enough that if it gets run more than once on the same log
file it will ignore the hits it has already processed. If you don't include
the '*', then savelogs might run before urchin runs, and urchin's statistics
will not accurate. However if you have urchin process the current log file
and past rotated logs, then you'll be sure to have accurate statistics. You
also won't have to coordinate urchin with when CPX rotates the logs.
You only must make sure that urchin is run more often then however many days
worth of rotated logs you configured CPX to keep. So if you have urchin run
daily, and CPX configured to keep 1 week's worth of rotated logs, then you
would be fine.
--
Jared Betteridge
Jonathan Duncan wrote:
How does CPX work with Urchin, as far as the log files go? I know CPX
installs savelogs, but does it set it up so that Urchin can still use the
logs?
Thanks,
--
Jonathan Duncan
http://www.nacnud.com
======================================================================
This is <cpx@xxxxxxxxxxxxx> <http://www.groupmail.org/lists/cpx/>
Before posting a question, please search the archives (see above URL).
======================================================================
This is <cpx@xxxxxxxxxxxxx> <http://www.groupmail.org/lists/cpx/>
Before posting a question, please search the archives (see above URL).