Hey guys.
Shawn Walker wrote:
> John Rice wrote:
> > Shawn Walker wrote:
> >> Remember that multiple attempts are made to contact a repository
> >> before giving up. I believe the default timeout is 30 seconds, and we
> >> try four times, so that would account for the two minutes.
> > Do we have any control over this? Would be nice to reduce it, 2 mins is
> > an awfully long time to wait in the GUI.
>
> I'd ask Krister about changing it before you do so, but, you can change
> each of the following as you see fit (these examples are from client.py):
>
> # This control how long the socket library waits before a timeout.
> socket.setdefaulttimeout(int(os.environ.get("PKG_CLIENT_TIMEOUT",
> "30"))) # in seconds
>
> # Override default PKG_TIMEOUT_MAX if a value has been specified
> # in the environment.
> global_settings.PKG_TIMEOUT_MAX = int(os.environ.get("PKG_TIMEOUT_MAX",
> global_settings.PKG_TIMEOUT_MAX))
>
> I'd ask you to not override these if the user has set the matching
> environment variables.
Admittedly I should read docs more than I do. :-) Regardless, now that I
know about these environment variables, I can see myself using them --
not decreasing their values, but rather increasing them. It's a drag,
when installing several large packages or doing an update, to walk away
for a while and return to discover that the install/update failed due to
a repo or my connection being flakey. I'd rather packagemanager keep
trying.
So assuming I'm following this thread correctly, on my systems the
progress dialog in question is going to be displayed for even longer
before failing, even after this issue is addressed?? :-)
Mind you, I'm not suggesting that this is a reason to override user-set
values; instead, I'm asking if perhaps there are progress dialogs which
a user should be able to cancel out of when that user has concluded that
the desired progress is not going to be made. The alternatives are
waiting it out and doing a forced quit. In the latter case (which seems
more appealing if you're beginning to suspect an app has become
non-responsive), packagemanager isn't given much of a chance to clean up
before being terminated. Wouldn't the addition of a Cancel button (or a
cute little 'x' next to the progress bar) solve the lengthy-timeout
problem without having to override anything?
Just my 2 cents, for what they're worth.... :-) Take care.
--Joanie
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
