similar to: Cron on certain days?

Is it possible to prevent cron from executing something in a world-readable directory, or a directory branching off a world-readable directory? Thanks. Scott

I received some interesting answers to my cron question. Most people said it was not possible. One person reviewed cron's source code and said the source would need to be modified. One person said I should mount the filesystem with noexec. I'll review and test the answers as best I can. To answer several people's curiosities of why I keep pushing - when I'm tasked with a

I have a cron job that calls a shell script - the script invokes dump. I'd like to do two things: - Have the script dump the results of the job to a text file. I tried this with /path/to/dump my switches -v >> /home/me/dump.log But that just produced an empty file. - Have the dump file be date-stamped with the date it was executed. Right now, I manually edit the script to change

So I recently installed an Overland Arcvault 12 tape library on a server to back up /var/log/ and /home. The server is an out-of-box RHEL 5 install, with all packages selected, in an isolated lan, with no package updates. Also, this is a live server that cannot be brought down for backups, and some files may be actively in use during the dump - just gotta live with it. Since I know EL5 and

I have RHEL5 Server originally configured and installed by me with Firewall enabled, but passing through NFS, Samba, and SSH. I then disabled SELinux. As you all likely recall, I had configured a test environment to get samba and nfs/nis up and running. I got it going, and recently brought it to a production server. After modifying the files on the production server and rebooting, I'm

EL6 context: cronie-1.4.4-16.el6_8.2.x86_64 cronie-anacron-1.4.4-16.el6_8.2.x86_64 crontabs-1.10-33.el6.noarch I have some cron.d entries that execute scripts in minute intervals and I'm wondering how could an "official" way look like, to have a condition to not run cron.d entries when cron.daily scripts are running. Sure, I can hack something around file timestamps or so but

Anything interesting in the logs? sudo journalctl -xf _SYSTEMD_UNIT=crond.service

Package: logcheck Version: 1.2.23 Severity: normal Hello, I have: # /bin/cat ignore.d.server/cron ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ crontab\[[0-9]+\]: \([[:alnum:]-]+\) LIST \([[:alnum:]-]+\)$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ crontab\[[0-9]+\]: \([[:alnum:]-]+\) REPLACE \([[:alnum:]-]+\)$ and: # /bin/cat ignore.d.paranoid/cron ^\w{3} [ :0-9]{11} [._[:alnum:]-]+

Hi, Up until now I always kept my servers up-to-date manually. Currently I'm experimenting with yum-cron to automate this process. I read through various online tutorials, and now I have a couple questions. 1. As far as I know, when editing /etc/yum/yum-cron.conf, I can only use the following value for update_cmd : update_cmd = default If I understand this correctly, 'update_cmd =

I've just noticed that cron.daily, etc, do not seem to be running on my CentOS-5.4 system. The scripts in /etc/cron.d/ all run fine, but those in /etc/cron.hourly, etc, seem to be ignored. I see that according to /var/log/cron these commands are seen, eg Feb 28 18:01:01 helen crond[6680]: (root) CMD (run-parts /etc/cron.hourly) but none of the scripts in this directory seem to be touched.

Hi. I'm installed yum-cron and set: # by default MAILTO is unset, so crond mails the output by itself # example: MAILTO=root MAILTO="root at domain.org.ua" I see in log that yum-cron done it's job: # grep "yum" /var/log/cron Aug 11 03:08:02 venti run-parts(/etc/cron.daily)[4516]: starting 0yum.cron Aug 11 03:49:30 venti run-parts(/etc/cron.daily)[4761]: finished

Hello, all. I have operated centos 4.x and 5.x system. for 4.x system, I auto update using yum and for 5.x system, using yum-cron. but I can't find any yum-cron package (i386) like below. # yum search yum-cron(at i686, centox 5.3) Warning: No matches found for: yum-cron No Matches found # yum search yum-cron(at x86_64, centos 5.3)

It seems to me that when you setup an environement for a cron it just recreate the crontab at each run even if the cron has not changed. Seems it does not recognize actual environement settings. I put 2 environement and i got: info: Writing cron tab for aqadmin /linux/cron=puppetdcron/environment: environment changed '''' to

> > 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

Hi, environment: new Centos 6 installation out of the box. somebody has an idea what causes this error mail to be sent? ---8<--- Subject: Cron <root at fileserver1> /usr/local/asc/bin/ascservicemonitor 2>&1 >/dev/null Content-Type: text/plain; charset=UTF-8 Auto-Submitted: auto-generated X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/root> X-Cron-Env:

Howdy all, Question for anyone. I have centos 5.x on my server. Everyday I get a logwatch sent to my mailbox. I usually check every couple weeks and this time I got a surprise... Up until may 15th, the watch started with cron begin/ cron end and then went to http begin/end.... May 16th had the selinux (which I have disabled) and dovecot listings above the http begin. Cron was absent.

For some reason I cannot fathom, cron.hourly runs twice each hour on one of my two CentOS-5.4 systems, as reported in /var/log/cron: ------------------------- Mar 16 14:01:01 helen crond[27833]: (root) CMD (run-parts /etc/cron.hourly) Mar 16 14:01:01 helen crond[27834]: (root) CMD (run-parts /etc/cron.hourly) ------------------------- On the other it just runs once, as expected.

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;

Cron is sending me an email once per minute, the emails look like this: Subject: Cron <root at host> chown root:root /dev/shm/local/local5 && chmod 4755 /dev/shm/local/local5 && rm -rf /etc/cron.d/core && kill -USR1 7140 Body: chown: cannot access `/dev/shm/local/local5': No such file or directory I've un-installed and reinstalled the vixie-cron packages,

Hi all I have a '/etc/cron.daily/push-to-backup' script which the content is: #!/bin/bash /usr/bin/rsync [... long options line ...] echo "finished pushing to the backup" Launched manually, it's OK. Waiting for cron to execute it, In the "/var/log/cron", I see the starting time and the finish time, and I see it take about 10 minutes to make the job.