While automagically dropping application config files into the /etc/logrotate.d directory looks good, well it doesn't work as well as it should. Because you never know how the application configuration is setup or timed, anytime you add an additional configuration file to the directory logrotate will fail for ALL APPLICATIONS in the /etc/logrotate.d directory until it has been found and removed. Putting even a hidden file into /etc/logrotate.d when updated will cause failure until found. Logrotate reads *all* files in that directory hidden or not then attempts to process them. In the recent past it was the ._cfg file from mysql that did the damage. Thanks
Qa/Basesytem people - your thoughts please.
why not just fix logrotate to ignore hidden files (anything that begins with a '.') doesnt seem that big of a deal
Sounds good SpanKY. Unfortunately I'm not really available (http://dev.gentoo.org/devaway) nor have I really anything to do with logrotate (sure I fixed the Manifest once but that hardly counts as maintenance). David if you want to attach a patch to the effect of comment #2 please do so and this will get fixed a lot quicker.
Created attachment 57348 [details, diff] ignore-hidden.patch try this patch out please ... it's for logrotate-3.7 ... ive never used logrotate myself ;)
This seems to be in logrotate already.
You're probably correct since the problem sat for two and a half years without an update.
David.Huff: it's in the source, I checked.
