similar to: CentOS 5 cronjobs

On Thursday, August 21, 2014 12:00:03 centos-request at centos.org wrote: > Re: [CentOS] SELinux vs. logwatch and virsh > From: Daniel J Walsh <dwalsh at redhat.com> > To: CentOS mailing list <centos at centos.org> > > On 08/18/2014 02:13 PM, Bill Gee wrote: > > Hi Dan - > > > > "ausearch -m avc -ts recent" produces no output. If I run it

On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings <billings at negate.org> wrote: > On Tue, Oct 13, 2015 at 06:24:19AM +0000, C. L. Martinez wrote: >> For example: logwatch. Logwatch sends a daily email report about >> system's health. I didn't received this email from October 9th ... and >> email configuration is ok. > > So your problem is that cron jobs

zep wrote: > On 10/13/2015 09:54 AM, C. L. Martinez wrote: >> I haven't entries in conrtab's users file at this moment, but I have >> done a test: * * * * * ls -la, and it is not triggered. But like I say >> before, installed system cronjobs like logwatch task are not triggered > > I'd say that crontab doesn't actually prove that the job isn't being

On Mon, Oct 12, 2015 at 12:15 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 10/11/2015 09:38 AM, C. L. Martinez wrote: >> >> That's the problem. There is no error but any cron job configured runs.. >> And this is the cuestion: why any cron job works?. > > > It's not clear what you're asking. It would help if you replied with an >

On Tue, Oct 13, 2015 at 1:45 PM, Richard <lists-centos at listmail.innovate.net> wrote: > >> Date: Tuesday, October 13, 2015 13:41:56 +0000 >> From: "C. L. Martinez" <carlopmart at gmail.com> >> >> >> On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings >> <billings at negate.org> wrote: >>> On Tue, Oct 13, 2015 at

I got the fail2ban from epel. There were a number of issues relating to using a log file... logwatch was looking for both fail2ban and fail2ban.log logrotate file fail2ban added looked for fail2ban.log and then reset itself to syslog fail2ban itself went to syslog, over riding its fail2ban.log. took a while, but I use /var/log/fail2ban now, that finally worked through logrotates and logwatch.

I've been taking a look at how RedHat (and CentOS) handles logrotate. According to the man page, logrotate is supposed to be fired by cron. But when I look at root's crontab $ sudo crontab lu root no crontab for root What exactly fires logrotate (and other scheduled events like "logwatch", which ends up in root's inbox)? === Al

On Tue, Oct 13, 2015 at 02:05:47PM +0000, Richard wrote: > > > >> If not triggered, you might want to show your crontab entries. > > > > I haven't entries in conrtab's users file at this moment, but I > > have done a test: * * * * * ls -la, and it is not triggered. But > > like I say before, installed system cronjobs like logwatch task > >

Hi, Last year, I installed Asterisk 10.4.2 and enabled logrotate on daily basis which was working perfect. Now in couple of months back, the logrotate feature is not working at all but simply appending the logs in 'messages' file. Listing down down the configuration for logrotate below; /var/log/asterisk/messages { missingok rotate 5 daily postrotate /usr/sbin/asterisk -rx 'logger

Hi, just to avoid re-inventing the wheel, is there any document that can help me reduce even further a "minimum" installation of Centos 4.4 (BTW can you say 600mb is minimum)? I am in the process of creating a small Centos-4.4-based Asterisk box and I need to boot it from a CF card. Deleting useless packages will help me do what i want. Example: even a minimum install of Centos 4.4 (or

Hi, just to avoid re-inventing the wheel, is there any document that can help me reduce even further a "minimum" installation of Centos 4.4 (BTW can you say 600mb is minimum)? I am in the process of creating a small Centos-4.4-based Asterisk box and I need to boot it from a CF card. Deleting useless packages will help me do what i want. Example: even a minimum install of Centos 4.4 (or

Hello I am trying to get logwatch working on CentOS 8. System is fully updated. Usually install minimal version and then add only necessary with yum. On CentOS 7: install logwatch and get daily logwatch report on mail. On CentOS 8: install logwatch but no way to get mail. Am I doing something wrong? Or miss something? Thanks in advance Blaz

> Date: Tuesday, October 13, 2015 13:54:28 +0000 > From: "C. L. Martinez" <carlopmart at gmail.com> > > On Tue, Oct 13, 2015 at 1:45 PM, Richard > <lists-centos at listmail.innovate.net> wrote: >> >>> Date: Tuesday, October 13, 2015 13:41:56 +0000 >>> From: "C. L. Martinez" <carlopmart at gmail.com> >>>

> Date: Tuesday, October 13, 2015 13:54:28 +0000 > From: "C. L. Martinez" <carlopmart at gmail.com> > > On Tue, Oct 13, 2015 at 1:45 PM, Richard > <lists-centos at listmail.innovate.net> wrote: >> >>> Date: Tuesday, October 13, 2015 13:41:56 +0000 >>> From: "C. L. Martinez" <carlopmart at gmail.com> >>>

On Tue, Oct 13, 2015 at 1:58 PM, Richard <lists-centos at listmail.innovate.net> wrote: > > >> Date: Tuesday, October 13, 2015 13:54:28 +0000 >> From: "C. L. Martinez" <carlopmart at gmail.com> >> >> On Tue, Oct 13, 2015 at 1:45 PM, Richard >> <lists-centos at listmail.innovate.net> wrote: >>> >>>> Date: Tuesday,

On 10/13/2015 04:44 PM, zep wrote: > > > On 10/13/2015 09:54 AM, C. L. Martinez wrote: >> I haven't entries in conrtab's users file at this moment, but I have >> done a test: * * * * * ls -la, and it is not triggered. But like I say >> before, installed system cronjobs like logwatch task are not triggered >> ...

On Tue, Oct 13, 2015 at 06:24:19AM +0000, C. L. Martinez wrote: > For example: logwatch. Logwatch sends a daily email report about > system's health. I didn't received this email from October 9th ... and > email configuration is ok. So your problem is that cron jobs *DO NOT* run? Because every message you've sent so far has said that all jobs run. -- Jonathan Billings

> Date: Tuesday, October 13, 2015 13:41:56 +0000 > From: "C. L. Martinez" <carlopmart at gmail.com> > > > On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings > <billings at negate.org> wrote: >> On Tue, Oct 13, 2015 at 06:24:19AM +0000, C. L. Martinez wrote: >>> For example: logwatch. Logwatch sends a daily email report about >>>

I've been noticing yum updates on several servers I manage over the last few weeks, which I know I didn't perform and could not explain until this morning. At first I suspect a break-in, but found no other evidence or reason an intruder would run the yum updates I was viewing. Yum updates are logged in /var/log/yum.log, which is what Logwatch scans. Seems that the format of the log

Is there a way to list the packages that are in a "base" install, but that are not in a "nobase" (core) install? I did a nobase install, then ran "yum groupinstall Base", but this just lists everything in base, including the core packages. Mainly, I'm just looking to audit the packages, and add only necessary ones back to a nobase install. So far, I've