Paul Howarth wrote:
Gustavo Seabra wrote:
On 4/13/05, Paul Howarth <paul@xxxxxxxxxxxx> wrote:
On Tue, 2005-04-12 at 13:17 -0500, Aleksandar Milivojevic wrote:
Paul Howarth wrote:
So the answer to your original question is "roughly sometime
between 4am
and about 6:15am".
Also, the cron job calls yum with "-e 0" option. That means if there
were any errors and your system is not updated, you are not going
to be
told anything about it... Removing "-e 0", and changing "-d 0" to "-d
1" might be good idea. "-d 1" will produce output only if yum was
acutally doing something, so if any packages were actually upgraded,
root (or whoever root is aliased to) will get some kind of report
in the
mailbox.
You'd get a report about packages installed/updated/removed using yum
from logwatch if it wasn't for:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140429
If you make the changes mentioned in the bugzilla, it does work. It's
been working fine for me for a long time now.
I know; comment #12 about the RPM containing the patch is by me...
Paul.
I'm glad you all brougth that up. I am afraid of playign with rpms in
any way that wil ham yum. I was looking for the script in question on my
system and I just couldn't seem to find them. Where should they be?
