Bug#744093: awstats: Using the multiple-config schema results in cron spamming with errors
reopen 744093 retitle 744093 provide a better documentation for miltiple stats tag 744093 -patch thanks On Thu, Apr 10, 2014 at 01:16:52PM +0200, Martín Ferrari wrote: > >> 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. > > > > I fail to see the words "all local changes". Instead, I see > > exactly same what I told you below: > > If you read "leave awstats.conf alone", clearly that means not modifying > it. It says clearly to put server settings in .local and site settings > in the other files. Are you actually reading this? I see also: -->8-- To handle multiple stats (eg. using VirtualHosts in Apache) you should... 1) Place all *additional* configs in /etc/awstats/. 2) Name the *new configs* "awstats." + whatever you want + ".conf" (eg. "awstats.example.com.conf"). But avoid "awstats.awstats.conf". [...] -->8-- So, it's all about *additional* vhosts. The main vhost supposed to be already configured - please don't consider every single line of README.Debian separately. But I admit, it maybe a good idea to use better wording. > >> 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? > > > > Put this in some awstats.*.conf. Why you want to make this host > > to be the default one (main host)? > > Because it might make sense to do so. Why? There is some design pattern for multiple hosts config: awstats.conf - main site awstats.*.conf - others, they include the first one. Can you understand this once and follow this pattern? Yes, you can. Can you suggest a better solution? (Keep in mind single-config scenario!) Then, please go ahead. But your patch is not acceptable for now. And I'm not sure if there is a documentation issue, that's why this bug was closed. End of story. > In any case, you are harming Debian. Maybe. If you are sure you can do my job better - please go ahead, take the package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744093: awstats: Using the multiple-config schema results in cron spamming with errors
On 10/04/14 13:03, Sergey B Kirpichev wrote: > On Thu, Apr 10, 2014 at 12:53:32PM +0200, Martín Ferrari wrote: 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. > > I fail to see the words "all local changes". Instead, I see > exactly same what I told you below: If you read "leave awstats.conf alone", clearly that means not modifying it. It says clearly to put server settings in .local and site settings in the other files. Are you actually reading this? >> 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? > > Put this in some awstats.*.conf. Why you want to make this host > to be the default one (main host)? Because it might make sense to do so. Or because some day I chosen that one to be the main host (only because you are asking me to do such a thing, since what I have been asking you is NOT TO MAKE THAT CHOICE), and then requirements change. >> So, the only way to do this, is to copy *all* the settings in every >> file, and not include awstats.conf at all. > > As I said - you have at least one another option. Now you are just being obtuse. If you want to close the bug, make my day. You either don't understand what I am writing or you only care about being right. In any case, you are harming Debian. -- Martín Ferrari (Tincho) signature.asc Description: OpenPGP digital signature
Bug#744093: awstats: Using the multiple-config schema results in cron spamming with errors
On Thu, Apr 10, 2014 at 12:53:32PM +0200, Martín Ferrari wrote: > >> 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. I fail to see the words "all local changes". Instead, I see exactly same what I told you below: > >> 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? Put this in some awstats.*.conf. Why you want to make this host to be the default one (main host)? > So, the only way to do this, is to copy *all* the settings in every > file, and not include awstats.conf at all. As I said - you have at least one another option. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744093: awstats: Using the multiple-config schema results in cron spamming with errors
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
Bug#744093: awstats: Using the multiple-config schema results in cron spamming with errors
> 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). > Also, you are encouraged to put all your local changes in > awstats.conf.local, to have painless upgrades. Can you quote this? > 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? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744093: awstats: Using the multiple-config schema results in cron spamming with errors
On 10/04/14 11:36, Sergey B Kirpichev wrote: > On Thu, Apr 10, 2014 at 04:08:06AM +0200, Martín Ferrari wrote: >> I have configured awstats using one of the recommended schemes in >> README.Debian, namely: using one small conffile per virtual-host that also >> includes the default awstats.conf. > > There is no such a scheme. Please read this: > -->8-- > [...] > -->8-- > > So, in this scheme - you should modify the default awstats.conf as well. Well, it does not make much sense, it would be inconsistent with the rest.. Also, you are encouraged to put all your local changes in awstats.conf.local, to have painless upgrades. >> This is a great way to have tidy >> configuration files, but it has a very annoying drawback: the cronjobs still >> try to use the unmodified awstats.conf file, and send me an email about this >> every 10 minutes. > > Can you fix these emails by configuring awstats.conf as one of vhosts? Yes, I could. But then again, which one is it? Also, if I make changes in that file, I need to make sure to revert them in all the other files which include it.. It is not good for maintenance, it is confusing and a bit untidy. > Please reopen this bugreport if the answer is no. Also, if you find > the documentation is not clear about the awstats.conf in this use case - > please > suggest changes (patches welcome). I think it is not clear in that sense, because it is not what one would expect. I would add a explicit warning about this. Which still does not make me very happy... Me, I will keep modified scripts, which then I will need to repatch on every upgrade.. -- Martín Ferrari (Tincho) signature.asc Description: OpenPGP digital signature
Bug#744093: awstats: Using the multiple-config schema results in cron spamming with errors
Package: awstats Version: 7.2+dfsg-1 Severity: minor Hi, I have configured awstats using one of the recommended schemes in README.Debian, namely: using one small conffile per virtual-host that also includes the default awstats.conf. This is a great way to have tidy configuration files, but it has a very annoying drawback: the cronjobs still try to use the unmodified awstats.conf file, and send me an email about this every 10 minutes. I would like to have a mechanism to disable the use of that file, or to automatically disable it when per-host configuration files are present. I undestand this might be problematic for backwards compatibility, so a variable in /etc/default/awstats might be used. Thanks. -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (900, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages awstats depends on: ii perl 5.14.2-21+deb7u1 Versions of packages awstats recommends: ii coreutils 8.13-3.5 pn libnet-xwhois-perl Versions of packages awstats suggests: ii apache2 2.2.22-13+deb7u1 ii apache2-mpm-worker [httpd] 2.2.22-13+deb7u1 pn libgeo-ipfree-perl ii libnet-dns-perl 0.66-2+b2 ii libnet-ip-perl 1.25-3 ii liburi-perl 1.60-1 -- Configuration Files: /etc/awstats/awstats.conf.local changed [not included] /etc/cron.d/awstats changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
