On Thu, 27 Jul 2023, 10:15 phep, <p...@wakzo.net> wrote: > > the -L option does not overrules anymore the default > logfiles list as stated in the manpage, it now extends it. >
true - we should perhaps clarify the documentation to make this clearer > We are impacted here since in addition to logcheck standard > configuration we use a second set of applications specific log > files for specific logcheck examinations run with a different > cron periodicity than the standard one. (it's nice to hear about people doing things like this - i have some thoughts about new features so good to have some understanding of use-caes so we dont break this kind of thing by mistske!) As you might have guessed, this implies the lines in > logcheck.logfiles.d/journal.logfiles are all commented out in > our configurations, we only use syslog.logfiles. > > Would you mind modifying the logcheck script so that the -L > option keeps working as a complete alternative to > logcheck.logfiles, as it used to? > i think there is a better solution already available you can use the -D option to avoid the standard the logfiles.d directory - set it to -L new.file -D /dev/null or to any empty directory. we do this with /dev/null in the debian tests so i am confident it works, if it doesnt that is a bug! (i think we should say this in the documentation ) as you say in your other mail, this isnt a change in bookworm just more obvious now we are using the .d directory. thanks for the report!
