I just installed logwatch on an etch fresh install Directories /etc/logwatch and subdirectories are empty I suggest post-inst should run the commands listed in /usr/share/doc/logwatch/README, ie : mv local.conf /etc/logwatch/conf touch /etc/logwatch/conf/logwatch.conf touch /etc/logwatch/conf/ignore.conf touch /etc/logwatch/conf/override.conf I am using Debian GNU/Linux testing/etch, kernel 2.6.17-2-686 Cheers for the work anyway.
severity 391720 wishlist thanks Ka Teznik schrieb: Severity completely crazy. Or can you justify? No, I won't. I have not yet decided if I will ship an empty comfiguration file. However, it's documented anyway, and if I start adding some empty configuration files I might need to add all. The only possible justification would be that the upstream installation script adds them (at least the empty ones) in 7.3.1, so this might happen (but probably will contain some basic information why they exist), but not for etch.
Le Dimanche 8 Octobre 2006 20:54, Willi Mann a écrit : I was believing this rendered logwatch unable to function properly. I saw later that default config is ok. Sorry for this mistake, severity wishlist is then ok. May I suggest you just install the default local.conf ? It's not empty, and some sysadmin (like me) are used to edit files in /etc/whatever just after installing... Thanks for your work !
Hi! Sorry to bother you with that after 6 month but: What did you mean by local.conf .. not empty? As far as I can see, all non-empty files and the directory layout are created. Do you still miss anything? I would like to avoid empty files. Willi
Le 23 04 2007, à 12:27:13 +0200, Willi Mann (willi@wm1.at) disait: Hi, Sorry to answer late. As I remember the problem, the file local.conf wasn't created by default install. Il the /usr/share/doc/logwatch directory you can found a file with all the option explained and positionned to the default. That's what I mean by "not empty". If this file was copied in /etc/whatever, one can configure logwath by simply editing this file, and not have the burden to find a sample local.cf to copy there before configuring logwatch. As stated, this is only a whishlist :-) Cheers,
Hello, I'd like to comment on the "logwatch doesn't install default config" bugreport. Let me start by describing the problem I had: On a machine of ours logwatch was using a really weird domain in the sender address (From: ...). I've got no clue where it got it from. So I wanted to configure it. But from the documentation I could not find a hint how to do that. The closest information I found in the provided docs and through online search was to modify logwatch files directly in /usr/.../logwatch. Well, that certainly can't be a good way to do it. Then I found http://www.debianhelp.co.uk/logwatch1.htm and things cleared up. So I'd like to suggest to provide a /etc/logwatch/conf/logwatch.conf file as exemplified by that article, that contains all the default logwatch settings and can be changed to the admin's preferences and needs. Thanks, *t