On 10/04/14 12:16, Sergey B Kirpichev wrote: >> Well, it does not make much sense, it would be inconsistent with >> the rest.. > > But it is consistent with "one host" scenario (i.e. without > awstats.*.conf).
That's why I am saying to enable this only when using multiple hosts.
>> Also, you are encouraged to put all your local changes in
>> awstats.conf.local, to have painless upgrades.
>
> Can you quote this?
Probably I was confused about the upgrades, but you are still encouraged
to leave the main file untouched:
This way you can leave awstats.conf alone, and put your
server-specific settings into awstats.conf.local, and your
site-specific settings into each awstats.[site_name_here].conf
file.
>> Yes, I could. But then again, which one is it?
>
> Use common sence, please. Options you want to modify in every
> awstats.*.conf - should go to awstats.conf. E.g. SiteDomain.
> Everything else - to awstats.conf or awstats.conf.local at your
> discretion.
>> Also, if I make changes in that file, I need to make sure to revert
>> them in all the other files which include it..
>
> Can you provide any example?
If my main host has some extra settings. Say, SkipHosts, because it
gets many hits from a monitoring tool, or you want to enable a plugin
for it... Where should I put that?
If it is in awstats.conf, it gets included everywhere. So I should be
cautious to undo that setting in all the other configs. If it is a
plugin setting, I don't think there is even a way to revert that setting.
If I add it in awstats.conf.local, it is the same thing, it gets added
everywhere. In fact, that's supposedly the purpose of the .local file.
So, the only way to do this, is to copy *all* the settings in every
file, and not include awstats.conf at all.
What you are suggesting goes contrary to what is suggested in the
README. So, I think you should either remove those suggestions, or fix
this issue.
--
Martín Ferrari (Tincho)
signature.asc
Description: OpenPGP digital signature
