Sunil Ghai wrote:
>> I'm not clear on whether the 'throttle' and 'bandwidth' configuration would
>> apply to yum-updatesd. It would still not be a dynamic adjustment but if
> users
>> knew how this worked it might be a good enough solution.
>
> That would not be the solution in real sense. What if someone wants to
> download another important file? A mechanism is needed to stop downloading
> the updated packages when the file is being downloaded. When it is done, we
> can resume updating the system.
>
>> We have TCP Low Priority� congestion algorithm in kernel. yum-updatesd
>> should request it on downloading socket via setsockopt(), as per commit
>> bc0efe7b46174fa3cadf00ac64e4a751cc4619fd .
>
> This might help me. Could you please provide me some more pointers?
>
>> One problem I see with this is that bandwidth statistics from are reset
> when
>> you reboot the machine. Unless you keep the machine up all the time it will
> lose track
>> of the exact amount of bandwidth used up. Maybe another daemon will need to
> keep track of
>> this?
> We actually don't need this kind of thing. For example, if currently 60% of
> the bandwidth is in usage, 40% is idle, we can use this idle bandwidth to
> download updated packages.Once the list of updated packages has been
> prepared, we can start downloading them and if the user shuts down the
> machine, next time we can resume downloading the packages where we left off.
> In this way user would never feel that the system is actually being updated,
> he or she will just get the message that "The system has been updated.."
The problem is you need to decide what 40% of 'the bandwidth' actually is, and
--
Andrew Farris <
lordmorgul@gmail.com>
www.lordmorgul.net
gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E A2E0 F0F6 E622 C99B 1DF3
No one now has, and no one will ever again get, the big picture. - Daniel Geer
---- ----