Don Maxwell wrote:
The /etc/cron.daily directory in FC6 does not have yum.cron as was in FC5.
I am still trying to figure out how to set up the nightly yum update as the way it was in FC5. I can write my own cronjob but there must be a better way to do this in FC6. With the default installation of yum-updatesd, it is not updating anything. So, perhaps, the thing to do is to edit /etc/yum/yum-updatesd.conf in such a way that it automatically install new updates?
Any help or pointer would be greatly appreciated.
Akemi
A Yagi at gmail wrote:
Don Maxwell wrote:
The /etc/cron.daily directory in FC6 does not have yum.cron as was in
FC5.
I am still trying to figure out how to set up the nightly yum update as the way it was in FC5. I can write my own cronjob but there must be a better way to do this in FC6. With the default installation of yum-updatesd, it is not updating anything. So, perhaps, the thing to do is to edit /etc/yum/yum-updatesd.conf in such a way that it automatically install new updates?
To most closely emulate the behaviour of the old yum cron job you need to edit /etc/yum/yum-updatesd.conf so that it says
# how to send notifications (valid: dbus, email, syslog) emit_via = syslog
# automatically install updates do_update = yes # automatically download updates do_download = yes # automatically download deps of updates do_download_deps = yes
You could also change the run_interval to specify a specific time rather than have it check every hour (or whatever the default is).
man yum-updatesd.conf has all the details.
Having said all of this, as someone else pointed out it still doesn't work at the moment. There's an open bug which is being actively worked on so hopefully a fix will be released soon.
Simon.
On Mon, 2006-11-06 at 13:03 +0000, Simon Andrews wrote:
man yum-updatesd.conf has all the details.
Having said all of this, as someone else pointed out it still doesn't work at the moment. There's an open bug which is being actively worked on so hopefully a fix will be released soon.
Simon.
If it does not work , why is it working on my machine until I disabled it?
Aaron Konstam wrote:
On Mon, 2006-11-06 at 13:03 +0000, Simon Andrews wrote:
man yum-updatesd.conf has all the details.
Having said all of this, as someone else pointed out it still doesn't work at the moment. There's an open bug which is being actively worked on so hopefully a fix will be released soon.
Simon.
If it does not work , why is it working on my machine until I disabled it?
Which bit works for you? Can you get it to download and apply updates automatically (ie the same as the yum cron used to do), or does it just notify you that updates are available?
If it all works for you can you add the details of your setup to the bug report at:
https://bugzilla.redhat.com/212507
...maybe we can figure our what the systems which are failing have in common.
Simon.
On Tue, 2006-11-07 at 11:29 +0000, Simon Andrews wrote:
Aaron Konstam wrote:
On Mon, 2006-11-06 at 13:03 +0000, Simon Andrews wrote:
man yum-updatesd.conf has all the details.
Having said all of this, as someone else pointed out it still
doesn't
work at the moment. There's an open bug which is being actively worked on so hopefully a fix will be released soon.
Simon.
If it does not work , why is it working on my machine until I
disabled
it?
Which bit works for you? Can you get it to download and apply updates automatically (ie the same as the yum cron used to do), or does it just notify you that updates are available?
If it all works for you can you add the details of your setup to the bug report at:
https://bugzilla.redhat.com/212507
...maybe we can figure our what the systems which are failing have in common.
Simon.
I already apologized to Rahul in previous message for confusing the issue. I was at the end of my patience when GNOME suddenly disappeared so I was not thinking clearly. I have never really seceded in using the automatic update feature. On my machine I send the notification to dbus and get a balloon saying that updates are available and I can do the updates.
As someone one commented in the bug reported the current program is over-engineered.. The simple cron entry worked pretty well.