Bug 855894

Summary:	cron daemon does not ignore rpmnew/rpmsave files
Product:	[Fedora] Fedora	Reporter:	Paul Wouters <pwouters>
Component:	cronie	Assignee:	Marcela Mašláňová <mmaslano>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	extras-orphan, mmaslano, notting, pertusus, tmraz
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-02 14:32:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul Wouters 2012-09-10 14:42:48 UTC

Description of problem:

when someone changes a cron job shipped in a package in /etc/cron*, and an update happens, there is now either an rpmsave or rpmnew file in addition to the cron file itself, resulting in TWO files executing almost identical content at likely the identical time - causing various problems

Is it possible to ensure rpmsave/rpmnew files are never actually executed by cron

Comment 1 Marcela Mašláňová 2012-11-22 12:30:19 UTC

Are you sure? I created job.rpmnew file and it wasn't executed.

There is cron option permit all jobs. Don't you have in config option -p?
cat /etc/sysconfig/crond

I can't reproduce it, so please give me better reproducer.