https://bugzilla.novell.com/show_bug.cgi?id=325564 Summary: Online update via http for ftp often errors for the incorrect timeout reason Product: openSUSE 10.2 Version: Final Platform: i386 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: alpha096@tpg.com.au QAContact: jsrain@novell.com Found By: Customer ALL updates regardless of source have an arbitrary time out value. This error is easily demonstrated when the update source is a local CD and the CD is not available - The error indicates that the update is unable to find the source file within the specified period of time. Unfortunately this arbitrary value is also applied to updates whos source is an HTTP or FTP and in the case where the source server the error OK, Skip, Abort etc window is displayed. The problem is that this arbitrary time-out value for locating the required media is of no value when the server of the update source is busy. What I am asking you to do is modify the script for the arbitrary time-out value when the source is an HTTP for FTP source. We just need to insert an IF statement in the timeout error to cope with increasingly busy update servers. The IF statement that needs inclusion could run something like this IF source == HTP or FTP* then skip timeout value and wait for noack from source before displaying error unable to read from Disk X. These values can be seen in the right click of the Zen-updater all inaccessible, I cannot confirm they are still visible in current software as I no longer use zen-updater in lieu of opensuse updater, however they are familiar to that software team. This small inclusion of the above also should apply to HTTPS or any source where comms indicates a noack or failure of response such as NFS. To apply time-out values to local sources makes perfect sense, however the error messages are a complete pain when the update server has not answered the request in the specified time period. Because of these occasional time-out error windows leaving an unattended online time lengthy update is just dangerous as the user may return and find an error just because the server has not responded quickly enough. If we fix this issue now we save much future heartache as online servers and number of user both increases with the success of the product. For example we never see a time out value applied to the lengthy process of the Novel server adding a new update source because the server is just busy. To apply a time-out value to an online update source and just take no notice of a comms noack or comms time-out makes no sense however I can understand why these errors sometimes plague us as stated above ALL update sources are treated basically the same so of the local CD is not available in the drive the user is prompted. To issue the same prompt to an online update source taking its time holds no logic and just creates headaches. There is no value in attaching my logs as the code if inspected would indicate the above. If you are not happy to examine the existing code for the above please just close this bug as wontfix. Many thanks Scott -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.