I've noticed on lower-end systems, that daily cron will peg a system for
a bit while that occurs. I had an ancient imac with ubuntu installed
that the apt update would hang the system for like a half-hour with an
old 400mhz ppc proc, consuming all cpu and memory, then swap and thus
disks too. I finally just disabled it, and shortly thereafter retired
the outdated system itself that it obviously had outlived its usefulness
vs. power drawn.
You likely have the same issue, just when using it, the update will slam
the system. Might be better off doing it manually, or setting the
update time for the cronjob to overnight when not using it.
-mb
On 09/19/2015 09:25 AM, Michael Havens wrote:
> the problem seems to have been checkapt.py . I tried to figure out
> what it does and it seems that it locks a database (apt's?). But it
> couldn't of been apt's as I wasn't running apt. Then I ran top again
> and it seemed to have corrected itself after 10 or fifteen minutes. Am
> I correct in what I think it does? Is it safe to kill if this happens
> again?
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)