Bug 60955 – whois not working after upgrade

Bug 60955 - whois not working after upgrade

Summary:	whois not working after upgrade

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	whois (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Nalin Dahyabhai
QA Contact:	Aaron Brown
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	FC3BugWeekTracker
	Show dependency tree / graph

Reported:	2002-03-10 09:31 EST by Jørgen Thomsen
Modified:	2007-04-18 12:40 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-09-27 16:43:20 EDT
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 Jørgen Thomsen 2002-03-10 09:31:12 EST

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461)

Description of problem:
After a recent upgrade I get this (also after compiling whois from the source)
[root@vennely root]# whois redhat.com
Address family not supported by protocol initializing protocol stacks?!?


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

How reproducible:
Always

Steps to Reproduce:
1. whois redhat.com
2.
3.
	

Actual Results:  Address family not supported by protocol initializing protocol 
stacks?!?


Expected Results:  Display of info on redhat.com

Additional info:

whois 1.0.9-1
It apparently appeared in connection to the upgrade which among other things 
included the perl 5.6.1 upgrade

Comment 1 Marcin Garski 2004-09-27 16:43:20 EDT

whois is no longer included in Fedora Core.
It has been replaced by jwhois.
Upgrade to lastest release of Fedora Core and try jwois, if this bug
still occur, please reopen.

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