Bug 652810 - latest run-parts broke /etc/cron.hourly and anacron
Summary: latest run-parts broke /etc/cron.hourly and anacron
Keywords:
Status: CLOSED DUPLICATE of bug 652268
Alias: None
Product: Fedora
Classification: Fedora
Component: crontabs
Version: 14
Hardware: Unspecified
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-12 20:44 UTC by John Saalwaechter
Modified: 2010-11-12 21:08 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-12 20:51:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John Saalwaechter 2010-11-12 20:44:07 UTC
Description of problem:

The run-parts in crontabs-1.11-1.20101109git.fc14.noarch assumes that its directory cmd line parameter has a trailing slash.  Here's the update:

 # Ignore *~ and *, scripts
-for i in $(LC_ALL=C; echo $1/*[^~,]) ; do
+for i in $(LC_ALL=C; echo $1*[^~,]) ; do
        [ -d $i ] && continue

This breaks the existing 0hourly crontab entry:

$ cat /etc/cron.d/0hourly 
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
01 * * * * root run-parts /etc/cron.hourly

Which in turn prevents /etc/cron.hourly/0anacron from running.  Which in turn prevents the rest of /etc/cron.{daily,weekly,monthly} from running.

It's unclear why the explicit slash was removed in the diff above.


Version-Release number of selected component (if applicable):
crontabs-1.11-1.20101109git.fc14.noarc


How reproducible:
100%


Steps to Reproduce:
1. Update to crontabs-1.11-1.20101109git.fc14.noarc
2. Confirm in /var/log/cron that /etc/cron.d/0hourly and all of /etc/cron.{hourly,daily,weekly,monthly} no longer run
3. Alternatively, simply run "# bash -x /usr/bin/run-parts /etc/cron.hourly"
  

Additional info:
Marking as urgent because of dropped cron jobs.

Comment 1 John Saalwaechter 2010-11-12 20:51:54 UTC
Hmmm... I searched bugzilla for "run-parts" prior to submitting this bug, and I only got two unrelated hits.  Then after logging in and filing this bug, I see nine hits, and that this is a dup.  I'm not sure why I got different search results before and after logging in.  Anyway, marking as dup.

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

Comment 2 James Laska 2010-11-12 21:08:54 UTC
Please note, and update is available in 'updates-testing' that attempts to resolve this issue.  Additional test feedback is needed before this update can be moved into 'updates'.  Thanks!

https://admin.fedoraproject.org/updates/crontabs-1.11-1.20101111git.fc14


Note You need to log in before you can comment on or make changes to this bug.