>>>>> "MM" == Matthew Miller <mat...@mattdm.org> writes:
MM> Can you send me what you're patching it to be?
I haven't patched it into F15 yet (still preparing the rollout) but this
is what I used in the F13 version:
--- 0yum.cron.quiet 2010-02-10 13:42:47.000000000 -0600
+++ 0yum.cron 2010-05-21 15:54:50.303916370 -0500
@@ -115,7 +115,7 @@
/usr/bin/yum $YUM_PARAMETER -R $RANDOMWAIT -e ${ERROR_LEVEL:-0} -d
${DEBUG_LEVEL:-0} -y update yum
/usr/bin/yum $YUM_PARAMETER -e ${ERROR_LEVEL:-0} -d ${DEBUG_LEVEL:-0} -y
shell $DAILYSCRIPT
fi
-} >> $YUMTMP 2>&1
+} | grep -v 'already installed' >> $YUMTMP 2>&1
if [ ! -z "$MAILTO" ] && [ -x /bin/mail ]; then
# if MAILTO is set, use mail command (ie better than standard mail with cron
output)
Honestly, though, this is probably more a bug in yum; there should
probably be a way to disable that message.
MM> Do you mean the ability to customize the yum-daily script in
MM> general, or the groupupdate functionality specifically?
I'm just lazy and trying to avoid changing anything. But....
MM> Offhand, I'm thinking there could be a "yum-cron groupupdate" action
MM> which would read a list of groups from
MM> /etc/yum/yum-cron/groupupdate.
I could live with that, too. And I'll admit to not having experimented
with the difference between groupinstall and groupupdate. Currently I
actually groupinstall the groups. (I want them installed after the
system boots for the first time, and I want any new packages added to
any of the groups to be installed at the next yum-cron run).
- J<
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
