FedoraThis forum is for the discussion of the Fedora Project.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Yep, that would probably be the auto update eating your bandwidth. Each boot will check for and download updated repository data (may also be a periodic check if the system is up long enough). When something has changed its usually a few MB per repository and when nothing has changed its much less traffic (no idea exactly how much though). Either way its a good idea to disable the auto updates on your limited bandwidth. To just disable the auto update checking you disable the service yum-updatesd. Better yet, you can uninstall the package yum-updatesd since you won't be using it anyway. I would advise running pup every week/2weeks/month and download what you consider the most important updates (at least security fixes).
Oh, sorry, are you a command line geek? Pup is just the standard GUI tool for package updates on Fedora. Pirut is the standard GUI tool for adding/removing packages. Both are just front-ends for yum. Or maybe you use some other GUI tool like yumex or the KDE one (forgot its name). Anyway, use some tool to check for updates at less frequent intervals.
Side note: I was just thinking, the whole point of this auto update tool is so you don't have to remember to check updates. Yum-updatesd could still be useful if you could configure it to check much less frequently. I checked the configuration file (/etc/yum/yum-updatesd.conf) and it stores its interval in seconds which has a default of 3600 seconds (1 hour) on my Fedora 7 system. Now it shouldn't be a problem setting this to an insanely huge value like 2592000 seconds (30 days), but I still think it will check on each boot. So if you reboot every day it will still run once every 24 hours, not once every 30 days. Not certain of this and I can find no documentation detailing startup behavior, but it seems to be how it works. Now I'm curios, if I figure this out I'll let you know.
List of long intervals converted to seconds if you feel like experimenting:
Default interval 1 hour (3600 seconds)
Weekly would be 604800 seconds
Bi-weekly 1209600 seconds
Monthly (30 days) would be 2592000 seconds
Ok, my idea won't work unless you plan on keeping your computer on 24/7. Once yum-updatesd starts it waits for the specified interval and then checks if there are updates. So with a long wait value (and assuming you don't leave your computer running for weeks at a time) it would never check for updates. Therefore, there would be no reason running the service in the first place.
Please forgive me if you were bored, confused, or just plain didn't care. The short story is, get rid of yum-updatesd to save your limited bandwidth, but remember to manually check for updates periodically.