Bug 62362 – Red Hat Network Daemon + long timeout with pcmcia network adaptor

Bug 62362 - Red Hat Network Daemon + long timeout with pcmcia network adaptor

Summary:	Red Hat Network Daemon + long timeout with pcmcia network adaptor

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Red Hat Public Beta
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	skipjack-beta1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Adrian Likins
QA Contact:	Jay Turner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-03-30 02:41 EST by Need Real Name
Modified:	2015-01-07 18:55 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-03-30 02:41:41 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2002-03-30 02:41:36 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/00200203

Description of problem:
During init the Red Hat Network Daemon takes a LONG time to time out when I try
to boot up without my pcmcia (netgear fa410tx) card plugged into the network. I
receive my IP via DHCP 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.boot up computer
2.get to init
3.I'm not hooked into the network so I'm not getting an IP through DHCP
4.Red Hat Network Daemon takes a LONG time to timeout
	

Actual Results:  The boot actually continued without a problem after Red Hat
Network Daemon timed out. But, the Red Hat Network Daemon timeout took almost 20
seconds when I'm not plugged into the network. 

Expected Results:  Red Hat Network Daemon should have timed out in one or two
seconds after it detected that no network connection was present.

Additional info:

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