search for: 0anacron

...y because it didn't need anacron at all, no? I've looked at yum history, it doesn't talk at all about anacron (but cronie-anacron) so it's not been installed and removed). > It's configured in /etc/anacrontab and is usually run once a day by the > script /etc/cron.hourly/0anacron - cron.hourly is still run by cron. > If the script doesn't exist, then anacron won't run and cron.daily etc > won't happen. There's a /etc/cron.d/0hourly here: ------------- # Run the hourly jobs SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root 01 * * * * root...

...uff in /etc/cron.{daily,weekly} > work until June 02? Don't know. But that's how cron.daily is processed and has been since CentOS7 was released. In fact I think CentOS 6 even used anacron. Perhaps you have inadvertently removed an important file like /etc/anacrontab or /etc/cron.hourly/0anacron > Probably because it didn't need anacron at all, no? I've looked at yum > history, it doesn't talk at all about anacron (but cronie-anacron) so > it's not been installed and removed). Yes, anacron *is* cronie-anacron > > > > It's configured in /etc/ana...

...So, service is running but what could happen that makes /etc/cron.* not > being fired? You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly is run using anacron, not cron. It's configured in /etc/anacrontab and is usually run once a day by the script /etc/cron.hourly/0anacron - cron.hourly is still run by cron. If the script doesn't exist, then anacron won't run and cron.daily etc won't happen. P.

...nitial install and first boot, any cron job configured had run (including cron tasks installed by some rpm packages). Last cron's entry log is: Oct 9 17:01:01 santgraal CROND[9014]: (root) CMD (run-parts /etc/cron.hourly) Oct 9 17:01:01 santgraal run-parts(/etc/cron.hourly)[9014]: starting 0anacron Oct 9 17:01:01 santgraal run-parts(/etc/cron.hourly)[9023]: finished 0anacron Oct 9 17:01:01 santgraal run-parts(/etc/cron.hourly)[9014]: starting 0yum-hourly.cron Oct 9 17:01:01 santgraal run-parts(/etc/cron.hourly)[9029]: finished 0yum-hourly.cron cron service is running without problems: [r...

I am getting /tmp/yum_save_tx.2017-12..... files in /tmp one every hour. What process is making these files ??? I have stopped PackageKit so its not running. I am running CentOS 7.4. With GNOME desktop. Thanks Jerry

Hello there, I've just noticed that scripts in /etc/cron.{daily,weekly,...} are not launched for several weeks (I noticed a `locate` not finding a recently added binary). Exactly, it's since June 02, and `# service cron status` says: Redirecting to /bin/systemctl status crond.service * crond.service - Command Scheduler Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled;

...a-update -rw------- 1 root root 235 Aug 3 05:30 sysstat cron.daily: total 12 -rwxr-xr-x. 1 root root 2239 Jun 9 2014 certwatch -rwx------ 1 root root 219 Aug 1 21:12 logrotate -rwxr-xr-x. 1 root root 618 Mar 17 2014 man-db.cron cron.hourly: total 4 -rwxr-xr-x 1 root root 392 Aug 3 11:33 0anacron cron.monthly: total 0 cron.weekly: total 0 Thoughts? Thanks, Jerry

...sysstat > > cron.daily: > total 12 > -rwxr-xr-x. 1 root root 2239 Jun 9 2014 certwatch > -rwx------ 1 root root 219 Aug 1 21:12 logrotate > -rwxr-xr-x. 1 root root 618 Mar 17 2014 man-db.cron > > cron.hourly: > total 4 > -rwxr-xr-x 1 root root 392 Aug 3 11:33 0anacron > > cron.monthly: > total 0 > > cron.weekly: > total 0 > > > Thoughts? Thanks, > > Jerry > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > Remember...

...parts /etc/cron.daily) Aug 18 04:02:01 xen-B1 anacron[25037]: Updated timestamp for job `cron.daily' to 2008-08-18 Aug 18 04:06:06 xen-B1 crond[2963]: (CRON) STARTUP (V5.0) the last line seems to be the reboot. here the content of my cron.daily folder. [root at xen-B1.blab:/etc/cron.daily]# ls 0anacron 0logwatch cups logrotate makewhatis.cron mlocate.cron prelink rpm tmpwatch I had also heartbeat running on the machines, after the last crash I thougt it was heartbeat that rebooted the machines, so I disabled it, but now I see it isnt heartbeat that causes these reboots. I use centos 5.1 w...

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

At the current time I am not subscribed to the mailing list. I have a blacklist that I got from www.peerguardian.net that is rather large ( 81 kb). When shorewall start command is issued it takes about 20 mins for it to load. Is this normal or should I do this another way? Also I noticed something very strange with shorewall .. I have cron do a shorewall restart command every 24 hours and

Hiya, Currently running Centos 4.2 x86_64 dist on a dual 3G xeon, 2G ram, scsi setupand everythings been running fine on it for some time. Then at 4am last night something kicked in (have mrtg running monitoring when) and since then its been running a load of about 1.5 (normally around 0.4). CPU usage is Cpu(s): 1.1% us, 0.6% sy, 0.0% ni, 97.9% id, 0.2% wa, 0.1% hi, 0.1%si. Can't see

...r root. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Session 33 of user root. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us CROND[12594]: (root) CMD (run-parts /etc/cron.hourly) Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12614]: starting 0anacron Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us anacron[12628]: Anacron started on 2016-06-30 Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12630]: finished 0anacron Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12633]: starting 0yum-ho...

...108 root root 12288 Mar 8 06:03 ../ lrwxrwxrwx 1 root root 28 Oct 19 2008 00-logwatch -> ../log.d/scripts/logwatch.pl* -rwxr-xr-x 1 root root 418 Nov 17 2007 00-makewhatis.cron* -rwxr-xr-x 1 root root 135 Feb 21 2005 00webalizer* -rwxr-xr-x 1 root root 276 Feb 21 2005 0anacron* -rwxr-xr-x 1 root root 125 Jan 2 01:59 apcstatus* -rwxr-xr-x 1 root root 123 Jan 2 01:56 apcstatus~* -rwxr-xr-x 1 root root 1042 Jan 29 2008 certwatch* -rwxr-xr-x 1 root root 94 May 2 2009 chkrootkit* -rwxr-xr-x 1 root root 74 May 6 2009 connections* -rwxr-xr-x...

On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth at 5-cent.us wrote: > Fred Smith wrote: > > On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote: > >> On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote: > >> > On Mon, Jun 20, 2016 at 01:34:30PM +0300, ????????? ???????? wrote: > >> > > >Can anyone of you provide further hints on what

Hi list, I'm a bit worried here. On a server, Centos 4.3 fully-patched SELinux activated, Osiris (a decentralized scanner for files changes on distant servers) signaled me several changes on files who were not (at first sight) affected by a recent update (the list is below). Is there a logic explanation for those changes to happen ? The "rpm -Va" command does not output md5sum