Bug 466018

Summary: /etc/cron.d not getting run.
Product: [Fedora] Fedora Reporter: Dave Jones <davej>
Component: cronieAssignee: Marcela Mašláňová <mmaslano>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mmaslano, pertusus, pfrields, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-08 14:53:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dave Jones 2008-10-07 18:23:48 UTC
I thought I had filed this bug already, but I can't find it, so I must have imagined it..

I have mrtg installed, which should be getting triggered every minute..

# cat /etc/cron.d/mrtg 
MAILTO=root
* * * * * root LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lock/mrtg/mrtg_l --confcache-file /var/lib/mrtg/mrtg.ok

however it doesn't get run at all.

stracing crond shows..
time(NULL)                              = 1223403721
time(NULL)                              = 1223403721
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
select(6, [5], NULL, NULL, {0, 0})      = 0 (Timeout)
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
time(NULL)                              = 1223403721
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGCHLD, NULL, {0x804a080, [], SA_RESTART}, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
nanosleep({60, 0}, {60, 0})             = 0

over and over. Never attempts to do anything related to that cron.d entry.

Comment 1 Marcela Mašláňová 2008-10-08 06:35:15 UTC
Did you update your selinux-policy? selinux-policy-3.5.8-6.fc10

It should have been fixed in #461988.

Comment 2 Dave Jones 2008-10-08 14:45:28 UTC
$ rpm -q selinux-policy
selinux-policy-3.5.10-3.fc10.noarch

ah yes, I couldn't find that bug for some reason when I searched.
Feel free to close this one and reopen the old one if you prefer.

Comment 3 Marcela Mašláňová 2008-10-08 14:53:15 UTC

*** This bug has been marked as a duplicate of bug 461988 ***