Frans Pop wrote: > This basically means that the current time-out is just too long for > practical use as is. > > An alternative option could be to make it possible to cancel the action, > just like we do for looking for a DHCP server. Yep, all network-facing progress bars in d-i need a cancel button. See other thread. ;-) Currently the timeout is just a standard tcp connection timeout, or in some cases, maybe several if it fails to connect to one server and tries another one. It should be easy enough to make this operation cancelable. It would be possible to enforce some shorter timeout (this is done in the code that runs hwclock, which can hang on some hardware, for example), but I don't feel that's the right choice in network operations since a network operation can legitimately take an arbitrary time to succeed. -- see shy jo
Attachment:
signature.asc
Description: Digital signature