Bug 177337 - yum.conf manual page information seems wrong
Summary: yum.conf manual page information seems wrong
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python-urlgrabber
Version: 4
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-09 20:26 UTC by Jasper O. Hartline
Modified: 2014-01-21 22:53 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-04-26 20:09:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jasper O. Hartline 2006-01-09 20:26:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Fedora/1.7.12-1.5.1

Description of problem:
I happen to be looking over a manual page and noticed it said "seconds" for a timeout value. The manual page is for yum.conf.

I think this is milliseconds, one because an ICMP echo request to www.google.com for example using the -A switch to ping, returns on average 30 milliseconds give or take 5 milliseconds, round trip.

Another reason I believe this value of "30" and "seconds" being a typo, is because I once helped a fellow on dialup, his yum was constantly failing, and we changed a timeout from the default to 90, this fixed the problem, he was on 256KBPS DSL.

I use a cable connection however, I don't see problems.
Thank you for your time, and if you could briefly explain the reason 30 seconds is the actual correct value.

Version-Release number of selected component (if applicable):
yum-2.4.1-1.fc4

How reproducible:
Didn't try

Steps to Reproduce:
1. man yum.conf
2. timeout default says "30 seconds"
3. 
  

Additional info:

Thanks.

Comment 1 Seth Vidal 2006-01-11 07:20:37 UTC
according to the socket.setdefaulttimeout docs in the python module it is in
seconds and since that is what yum is using, it is in seconds. reassigning this
to urlgrabber, just in case, though.



Note You need to log in before you can comment on or make changes to this bug.