|
Bugzilla – Full Text Bug Listing |
| Summary: | whois does not work as root | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Forgotten User ZhJd0F0L3x <forgotten_ZhJd0F0L3x> |
| Component: | Basesystem | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aschneck |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Component Test | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 97395 | ||
|
Description
Forgotten User ZhJd0F0L3x
2005-09-15 14:56:28 UTC
fatou:/suse/werner # rpm -qf /usr/sbin/whois sax2-tools-2.7-27 seife@strolchi:~> which whois /usr/bin/whois seife@strolchi:~> rpm -qf /usr/bin/whois whois-4.7.5-3 seife@strolchi:~> maintainer whois mmarek@suse.cz sorry, i did not get the funny part :-) Yes, the sax2 whois should probably be renamed. fixed *** Bug 139574 has been marked as a duplicate of this bug. *** Markus: Do you have renamed the whois command included
in the sax2-tools package?
No, i didnt renamed it, cause I didnt knew about. Also I dont understand why one creates a whois command that couldnt be run under root. And now, if we all know where the right one is, please try thos one with an ip address, there you'll see that it's working! Very hard to find that linux is more and more like a windows box :-( as I already said the old version of this whois program was installed to /usr/X11R6/bin and has been accidently moved to /usr/sbin because of those LSB policy. As fast as possible I renamed the program but unfortunately it was too late for the product cycle of 10.0. It is fixed since September the 15th and of course for stable. If you don't mind you can update sax from the following location: ftp://ftp.berlios.de/pub/sax/head-build/suse-10.0 I'm really very sorry it was my stupid mistake but it is fixed ah, ok I understand. But allow one further question, please. why doesnt the yast update fix this problem? isnt it possible th include it there? regards, axel |