similar to: What fires logrotate

I'm noticing that logrotate's default configuration for rotating /var/ log/secure and /var/log/messages partially fails if root's shell is set to /bin/tcsh (via chsh). (Running on CentOS 4.4; logrotate-3.7.1-5.RHEL4). What seems to be happening is that the logrotate.d/syslog postrotate command runs: /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null

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.

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

I am trying to get a logwatch summary emailed to a central address from a cron job. The tasd was copied verbatim from a system which does this already. Both are shown below. host1 crontab -l as root 45 7 * * * /usr/sbin/logwatch --service http --service imapd --service pop3 --service sshd --service vsftpd --service zz-disk_space --service zz-network --service zz-sys --mailto support at

The 2.04b rpm for rh60 ships with and installs a config file for logrotate (the samba.log file in the packaging/RedHat section). ===== /var/log/samba/log.nmb { postrotate /usr/bin/killall -HUP nmbd endrotate } /var/log/samba/log.smb { postrotate /usr/bin/killall -HUP smbd endrotate } ===== 1) I think that the use of "endrotate" is wrong. There is no

Hi guys, Logrotate is checked every day by cron.daily, right? I notice in logrotate.conf by default it's weekly. If I change it into monthly (now, on 12 of Feb), when will it do the monthly rotation? a. On 12 of March or b. On 1st of March? Thanks for any insight.

Hi, I'm trying to figure out which process is rotating my maillog every Sunday at 4:03 am. This happens on all of my centos 4 boxes. AFAICT, logrotate is not running. This is from a fairly minimal install, so I'm assuming this is a default process. --- [root at penguin ~]# ls -l /var/log/maill* -rw------- 1 root root 230603836 Sep 27 16:30 /var/log/maillog -rw------- 1 root

Is anyone else having major I/O peaks due to logrotate or other jobs running simultaneously across multiple guests. I have one KVM server running Centos 5.4 with local disk that is seriously suffering as most of the guests rotate their syslog at the same time. Looking at the KVM server I'm seeing 11:00:01 PM CPU %user %nice %system %iowait %steal %idle 03:40:01 AM

This was in root's mail on a newly-installed CentOS-5 system. To: root at beauregard.localdomain Content-Type: text/plain; charset="ANSI_X3.4-1968" Subject: Anacron job for 'beauregard.localdomain' cron.daily /etc/cron.daily/logrotate: error: sa-update:3 unknown option 'notifyempty' -- ignoring line ^

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

So, the question is, why can I rotate the log manually, but cron returns a permission error? Do I need to tell cron to run it as sudo or something like that? Ethon > On Nov 17, 2017, at 2:29 AM, Tom Hendrikx <tom at whyscream.net <mailto:tom at whyscream.net>> wrote: > > Hi, > > > Your crontab should normally mail you error output. But you can also run > the

> Date: Thursday, July 20, 2017 02:25:52 +0000 > From: Richard <lists-centos at listmail.innovate.net> > >> Date: Wednesday, July 19, 2017 23:31:10 +0000 >> From: Chad Cordero <ccordero at csusb.edu> >> >> It?s being rejected before it even reaches the mailbox, so >> forwarding won?t work.? Crond should really be using the MAILTO >>

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

Dear All, Currently i am using CentOS 4.4 Linux I have configured crontab to run cron.daily at 4:02 am 2 4 * * * root run-parts /etc/cron.daily On 4:02 am my pc is shutdown and i am boot-up my pc on 13:11:10 Please verify the system log messages from "/var/log/messages" file Jul 30 13:11:10 localhost syslogd 1.4.1: restart (remote reception). Jul 30

Howdy list, Hey does anyone know what the best cron job is to call logrotate to run the squid logrotations? -Or the subscribe address for a squid or logrotate mailing list (can't seem to find anything other than the usual MARC archives). I have this in /etc/logrotate.conf # rotate log files daily, they get too big otherwise, another story. daily # keep 8 weeks worth of backlogs e.g. 60

Dear All, Currently i am using CentOS 4.4 Linux Logrotate is not happen without -f option I have executed the following logrotate /etc/logrotate.conf manually and Logrotate command exit without any error messages If i executed with -f option then Logrotate will happen I am not sure why this is happening. Can some one throw light on this. Regards -S.Balaji

Hi all, I have a problem with logrotate and I don't know why. In /var/log/messages appears these errors: Apr 8 15:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 16:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 17:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 18:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8

Hi all: logrotate is broken on my stock 4.1 install. After hunting and hunting I found there is a bug filed with Redhat on the issue. logrotate fails becasue my /tmp partition is mounted noexec. I understand it is that way for security reasons. The box in question is on a dedicated hosting site and that's the way it was handed off to me, built. Some said setting TMPDIR=/var/tmp;export

Am 28.03.23 um 10:40 schrieb Rowland Penny via samba: > > > On 28/03/2023 08:40, Arnaud FLORENT via samba wrote: >> Hello >> >> >> i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using >> www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository >> >> >> everything is running fine but i have few log files in /var/log/samba/

On 28/03/2023 08:40, Arnaud FLORENT via samba wrote: > Hello > > > i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using > www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository > > > everything is running fine but i have few log files in /var/log/samba/ > are not handl by /etc/logrotate.d/samba > > log.samba-dcerpcd > >