Apup sitting on "reading scripts" for 2-3 hours...
Posted 14 January 2008 - 10:23 PM
Posted 14 January 2008 - 11:02 PM
The work flow of apup is something like this :
- apup starts.
- It immediately downloads a releases.list from AP's website.
- It then shows what releases are available.
- A user selects which release should be downloaded next.
- When a user done selecting, apup downloads one (or many) .script files according to what the user selected.
- The .script file(s) contains MD5 hashes of every updates/patches that apup will check to determine whether you already have the files or not.
- Then apup builds a download list based on what's not on your h/d.
But it's just that the more files that you have on your h/d, the longer apup will check for them.
Seems like apup hash checking routine is a rushed job compared to AP's, or it's probably due to simultaneous job of hash checking and generating a download list.
In this case, how long apup will process the scripts depends on the h/d and or CPU performance of a system.
But since I'm not the one creating apup, CMIIW.
Edited by sh1leshk4, 14 January 2008 - 11:03 PM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users