On Fri, May 01, 2009 at 12:33:35PM -0500, 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.
I'd agree with Shawn's reccomendation about respecting the user set
values. As part of the transport changes that I've already made, I put
some of these environment variables in packagemanager(1), for feature
parity with the client. Is this a fix that you need to have
immediately, or can it wait for the transport re-write to occur?
Given the two choices of defaults to override, I would choose the
maximum number of timeouts; however, be aware the getting timeout
messages tends to confuse users. I think we just had a bug show up
about this problem this week.
-j
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
