similar to: centos 4.7 - logwatch - and perl script applytaidate

On Mon, September 14, 2015 14:51, James B. Byrne wrote: > The Logwatch imapd service script distributed with CentOS-6 does not > generate anything when I run logwatch --service all on a cyrus-imapd > host. Is this expected behaviour? Is there a separate script for > cyrus-imapd or are their configuration options required to get the > existing script to work. > > I have found

Hello, I am using multiple files for logging activities for named daemon. The files are in /var/named/chroot/var/log/named/, for example /var/named/chroot/var/log/named/general.log. I am trying to make logwatch look into them. I have created /usr/share/logwatch/default.conf/logfiles/named.conf like this: LogFile = /var/named/chroot/var/log/named/general.log *ExpandRepeats *OnlyHost

On Sunday, April 19, 2015 15:46:29 Joseph L. Casale wrote: > > Can anyone point me to where my mistake is? > > First, you are creating overrides, or site specific definitions in the > platform directory. Don't do that, the distro owns and maintains this. Put > your new code in /etc/logwatch, man 8 logwatch for explanation. > > Finally, you don't show is the script

> Can anyone point me to where my mistake is? First, you are creating overrides, or site specific definitions in the platform directory. Don't do that, the distro owns and maintains this. Put your new code in /etc/logwatch, man 8 logwatch for explanation. Finally, you don't show is the script that actually does the parsing. The "service" and "log" definition

greetings like many, i get a daily logwatch email from "root" about 4AM last night, i rebooted a server from remote between midnight and 2AM and, uncle me, i received an extra logwatch from "anonymous" at the same machine can anyone explain or has anyone else else ever seen this behavior? just wondering and thanks in advance - rh -- Robert Hanson - Abba Communications

Semi Off Topic My searching hasn't found what I consider superior info, and we are wondering from others experience on this list... In the logwatch results we all see the info below on almost a daily basis I have taken the liberty of combining logwatch results from centos 4 and 5 machines for extra info and future searchability ----- Centos 4 ----- --------------------- httpd Begin

Re: centos 5 logwatch Has anyone ever looked into why verisign does this from these ips fairly frequently? It appears that it is some type of SSL probing the HTTP port, correct? Are they just gathering stats or something ? --------------------- httpd Begin ------------------------ A total of 2 sites probed the server 216.168.253.197 216.168.253.198 ..... The first ip is

On Thu, 2019-11-21 at 13:44 +0100, Adrian van Bloois wrote: > I wonder if there is a script to analyze logfiles for llogwatch and > sshguard? > Anyone knows? You can take an existing script, for another piece of software reported by Logwatch, retain the beginning and ending parts, and create your own version. The completed script should be placed in /etc to ensure it is not

On Sat, September 19, 2015 06:51, Tony Mountifield wrote: > In article > <d0000782c236fbee71045dad24a43def.squirrel at webmail.harte-lyne.ca>, James B. Byrne <byrnejb at harte-lyne.ca> wrote: >> After some experimenting I have observed that overriding settings from >> /usr/share/logwatch/default.conf/logwatch.conf in >> /etc/logwatch/conf/logwatch.conf does not

> Date: Sunday, April 09, 2017 08:36:17 -0400 > From: Robert Moskowitz <rgm at htt-consult.com> > > Logwatch is installed, and I am assuming by how empty /etc/logwatch > is that it is running from defaults, which I find in > /usr/share/logwatch/default.conf/services > > I want to customize ONE service. dovecot. > > Do I copy

After some experimenting I have observed that overriding settings from /usr/share/logwatch/default.conf/logwatch.conf in /etc/logwatch/conf/logwatch.conf does not produce consistent results. For example, if I replace the default detail configuration in etc/logwatch/conf/logwatch.conf with: Detail = High It does indeed change the level of detail from the default Low set in

I having a problem where Logwatch is not showing any events from the /var/log/secure log file. When I run logwatch --print --range today --service sshd --detail 10 --debug 10 the end result shows this: ... LogFiles that will be processed: [0] = secure [1] = messages Made Temp Dir: /var/cache/logwatch/logwatch.sOga48bL with tempdir export LOGWATCH_DATE_RANGE='today' export

On Mon, September 14, 2015 21:28, Always Learning wrote: > > On Mon, 2015-09-14 at 14:51 -0400, James B. Byrne wrote: > >> The Logwatch imapd service script distributed with CentOS-6 does not >> generate anything when I run logwatch --service all on a cyrus-imapd >> host. Is this expected behaviour? Is there a separate script for >> cyrus-imapd or are their

CentOS 6 (amd64) up to date with latest security / bug fixes. The logwatch reports come in plain text even though the config states HTML. <begin /etc/logwatch/conf/logwatch.conf> mailer = "/usr/sbin/sendmail -t" TmpDir = /tmp MailFrom = logwatch at example.com MailTo = admin1 admin2 admin3 Range = yesterday Detail = Medium HostName = www.example.com Print = No Output = mail

>-----Original Message----- >From: Ama Kalu [mailto:ama.kalu@cwlgroup.net] >Sent: Wednesday, November 19, 2003 9:07 PM >To: ''Tom Eastep'' >Subject: RE: [Shorewall-users] logwatch > >Thanks Tom and Andrew, > >About 2 months ago, I setup the most current (at the time) version of >logwatch, it required a service filter for IPTABLES which I did not have

After the upgrade to CentOS 5.9, all my CentOS 5 installations report only "Unmatched Entries" in the "yum" section of their daily logwatch mails. It seems the filter script /usr/share/logwatch/scripts/services/yum got broken: --------8<--------8<--------8<--------8<--------8<--------8<--------8< [root at dns01 ~]# /usr/sbin/logwatch --print --service yum

Logwatch is installed, and I am assuming by how empty /etc/logwatch is that it is running from defaults, which I find in /usr/share/logwatch/default.conf/services I want to customize ONE service. dovecot. Do I copy /usr/share/logwatch/default.conf/services/dovecot.conf to /etc/logwatch/conf/services and edit it there, or do I have to copy ALL default.conf/services/* there and modify

Maybe the format is set in sudo crontab -l Am Montag, 29. August 2016 schrieb Arun Khan : > CentOS 6 (amd64) up to date with latest security / bug fixes. > > The logwatch reports come in plain text even though the config states HTML. > > <begin /etc/logwatch/conf/logwatch.conf> > mailer = "/usr/sbin/sendmail -t" > TmpDir = /tmp > MailFrom = logwatch at

Hello, I have a couple of CentOS 5 servers, and third running in a FC6 domU. I've configured postfix on those servers to not deliver any email to the local system, but to instead relay mail to an internal mail server. I also set up /etc/aliases to send all mail to root to me, ksandhu. I can send mail on the command line, and I get it at my email address, delivered to the internal mail

Not sure if anybody noticed that logwatch is not reporting any stuff from /var/log/yum.log file. This is due to date format in log file (yum uses standard syslog date format, while logwatch script expects US date format). It seems that upstream doesn't ship with yum at all, so I guesss the problem was never detected there (and in most likeliness not applicable to it, although the upstream