Bug 40573

Summary:	lpr and netscape hang without network connection
Product:	[Retired] Red Hat Linux	Reporter:	dkaplan
Component:	netscape	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NOTABUG	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-05-14 18:28:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description dkaplan 2001-05-14 18:28:14 UTC

Description of Problem:
I have a laptop that is connected to a network sometimes and sometimes
not.  Both netscape and lprng hang if I dont have a network connection. 
LPRng hangs on boot up trying to look for the printers I assume.  I assume
this ends at some point, but I have never had the patience to wait. 
Netscape hangs when it is opened.  The only solution for the problem with
netscape that I have found is to convert to another linuxconf profile that
uses 192.168.1.??? addresses.  I assume it decides not to look when it sees
private addresses. 

How Reproducible:
Happens every time.

Steps to Reproduce:
1. Take your average workstation with network connection and unconnect it.
2. Reboot to see the lpr problem.  Make sure all the printers are network
printers - in particular, I was using smb printers.
3. To see the netscape problem, all you have to do is open it up.

Actual Results:
Hangs for a long time.

Expected Results:
It should keep looking probably, but in the background and in a way that
doesnt hold the whole machine hostage.

Additional Information:

Comment 1 Bill Nottingham 2001-05-14 18:31:23 UTC

It's attempting to do name resolution on any configured printers (in the
case of lpd), or its normal startup DNS checks (in the case of netscape.)

It's normal behavior, and in the case of netscape, unfixable.