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