On 01/25/2014 05:37 PM, Chris Murphy wrote:
Hmm, so this isn't working for me for some reason. Even though I've got it
disabled, it's still sucking down updates if gnome-shell runs. So I'm actually
not sure what this service does, or what I need to disable to prevent them from
being downloaded
On Jan 23, 2014, at 11:49 AM, Chris Murphy wrote:
>
> systemctl disable packagekit-offline-update.service
> systemctl stop packagekit-offline-update.service
Hmm, so this isn't working for me for some reason. Even though I've got it
disabled, it's still sucking down updates if gnome-shell runs.
On Thu, 23 Jan 2014 19:18:12 +
Phil Dobbin wrote:
> I take it running '# yum update' will still work?
>
As should yum-cron or yum-updatesd if installed.
___
Regards,
Frank
www.frankly3d.com
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription optio
On 23/01/14 18:49, Chris Murphy wrote:
On Jan 23, 2014, at 11:40 AM, Phil Dobbin wrote:
Hi, all.
I know this has been discussed on here before but I'm struggling to stop
'yumBackend.py' hogging the CPU & sending the load averages over 2.00.
I've disabled it
On Jan 23, 2014, at 11:40 AM, Phil Dobbin wrote:
> Hi, all.
>
> I know this has been discussed on here before but I'm struggling to stop
> 'yumBackend.py' hogging the CPU & sending the load averages over 2.00.
>
> I've disabled it via the GUI in
Hi, all.
I know this has been discussed on here before but I'm struggling to stop
'yumBackend.py' hogging the CPU & sending the load averages over 2.00.
I've disabled it via the GUI in Software & rebooted but it's still
running every five minutes.
Is the
On 03/13/2012 06:40 AM, Gene Smith wrote:
Since today's f16 update, yumBackend.py seem to being running 100% cpu
every few minutes. I think this also happened a few months ago but got
OK but now it seems to be back.
OK, here's where it's described:
https://bugzilla.redhat.com/
Since today's f16 update, yumBackend.py seem to being running 100% cpu
every few minutes. I think this also happened a few months ago but got
OK but now it seems to be back.
OK, here's where it's described:
https://bugzilla.redhat.com/show_bug.cgi?id=752564
I had set my kde