Bug 724888 - error in /etc/cron.daily/0yum.cron script, CHECK_ONLY=yes doesn't work
Summary: error in /etc/cron.daily/0yum.cron script, CHECK_ONLY=yes doesn't work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-22 07:49 UTC by Pavel Lisý
Modified: 2014-01-21 06:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-06 15:58:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Pavel Lisý 2011-07-22 07:49:16 UTC
Description of problem:
There is error in script which cause disfunction of settings in /etc/sysconfig/yum-cron

Version-Release number of selected component (if applicable):
yum-cron-0.9.2-2.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. set CHECK_ONLY=yes in /etc/sysconfig/yum-cron
2. system is updated every night instead of check only
3.
  
Actual results:
with this setting: CHECK_ONLY=yes
system is checked for update every night, sends mail info and then is updated

Expected results:
with this setting: CHECK_ONLY=yes
system is checked for update every night and sends mail info only

Additional info:
change line 15 in /etc/cron.daily/0yum.cron
from:
  source /etc/sysconfig/yum-cron
to:
  . /etc/sysconfig/yum-cron

Comment 1 James Antill 2011-07-22 14:07:23 UTC
 According to the bash man page "source" and "." are synonyms.
 Are you sure that is the only thing you changed to go from working to not-working?

Comment 3 Pavel Lisý 2011-09-06 13:21:59 UTC
It was my fault, there was another process making updates (in rpm package yum-autoupdate) and than I couldn't find this bugzilla record to cansel it. Sorry.

Comment 4 Pavel Lisý 2011-09-06 13:22:57 UTC
You should close this "bug". Thanks.


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