Patrick Shanahan wrote:
* Basil Chupin <blchupin@iinet.net.au> [01-29-09 03:21]:
smart on the other hand simply downloads whatever RPM/s are downloadable and if it/they are not downloadable smart skips it/them and continues with downloading the rest. You then restart smart to download the missed RPMs when, for example, you come back from shopping or wake up in the morning and see that the task hasn't been completed.
Another approach would be to continue on with the other packages and retry the errant operation after the others have completed their download. Perhaps a retry counter and only fail aftery all others have completed and/or failed > 2 times.
Good point. It would also be most useful if the user had control over 2 things: the number of retries and the delay time between retries. Only last week someone gave me what had to be done to control the delay before zypper issues the error message that the attempted download has timed out - and I have now set it to 20 seconds (prior to this you had time to mow the lawn, have a cup or two of tea, have an argument with the wife, make up and still had time to spare before zypper came up with the ERROR message). Reason for my setting zypper's response time is that my ISP has OFF PEAK and PEAK periods, and I try and do my updates/upgrades during the off peak period. Often zypper will "hang" close to the end of downloading often 100+ files, the off peak period is coming to the end and one has to sit and wait for b****** zypper to come up with the ERROR message before the rest of the downloads can be completed. GRRRRR! Ciao. -- "I do not instruct the uninterested; I do not help those who fail to try. If I mention one corner of a subject and the pupil does not deduce therefrom the other three, I drop him." Confucius -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org