Red Hat Bugzilla – Bug 327401
Last modified: 2007-11-30 17:12:18 EST
Description of problem:
yum-cron produces unexpected output if CHECK_ONLY=yes
Version-Release number of selected component (if applicable):
set CHECK_ONLY=yes in /etc/sysconfig/yum-cron, run /etc/cron.daily/yum.cron
You will see '^M' sequence on the screen if any updates are present because of
echo "`/usr/bin/yum -e 0 -d 0 -y -C check-update`^M"
touch $LOCKFILE is not an atomic operation, so it won't serve the purpose of
preventing two instances running if two processes will start exactly at the same
time. The proper solution would be mkdir $LOCKFILE 2>/dev/null || exit , well,
you got the idea.
Thanks for catching this bit of cut-n-paste disease, I should be using escape
characters rather than embedded ctrl sequences anyway. Fixing...
yum-cron-0.6-1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update yum-cron'
yum-cron-0.6-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.