Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fwd: crippling bug in jwhois #6

Open
jonasob opened this issue Jan 8, 2015 · 0 comments
Open

Fwd: crippling bug in jwhois #6

jonasob opened this issue Jan 8, 2015 · 0 comments

Comments

@jonasob
Copy link
Owner

jonasob commented Jan 8, 2015

---------- Forwarded message ----------
From: Jonas Öberg
Date: 8 January 2015 at 09:18
Subject: Fwd: crippling bug in jwhois #jwhois-bug
To: trigger@recipie.ifttt.com

---------- Forwarded message ----------
From: Eesger Toering (Knooppunt)
Date: 24 February 2014 at 14:59
Subject: crippling bug in jwhois
To: bug-jwhois@gnu.org

Hello,

I made an error in a piece of software I wrote. Each hanging process
demands 100% CPU power. I was testing a bit and a dozen process were
fighting for resources, resulted in crippled server!

-------------------------- ps axuw USER
-------------------------------- rs=0 12:52
Duur(m) PID PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
31 14528 14528 27.8 0.0 8628 1012 ? R 12:21 8:44
/usr/bin/whois -h 1 knoop.nl
31 14672 14672 27.2 0.0 8628 1012 ? R 12:21 8:26
/usr/bin/whois -h 1 knoop.nl
30 15106 15106 25.2 0.0 8628 1016 ? R 12:22 7:38
/usr/bin/whois -h 1 knoop.nl
29 15289 15289 24.4 0.0 8628 1012 ? R 12:23 7:18
/usr/bin/whois -h 1 knoop.nl
29 15694 15694 23.6 0.0 8628 1012 ? R 12:23 6:52
/usr/bin/whois -h 1 knoop.nl
28 15844 15844 23.0 0.0 8628 1016 ? R 12:24 6:37
/usr/bin/whois -h 1 knoop.nl
28 16187 16187 22.8 0.0 8628 1012 ? R 12:24 6:26
/usr/bin/whois -h 1 knoop.nl
27 16524 16524 22.4 0.0 8628 1012 ? R 12:25 6:14
/usr/bin/whois -h 1 knoop.nl
25 17571 17571 21.8 0.0 8628 1012 ? R 12:27 5:38
/usr/bin/whois -h 1 knoop.nl
25 17642 17642 21.6 0.0 8628 1016 ? R 12:27 5:32
/usr/bin/whois -h 1 knoop.nl
25 17730 17730 21.8 0.0 8628 1016 ? R 12:27 5:33
/usr/bin/whois -h 1 knoop.nl
25 17804 17804 21.7 0.0 8628 1012 ? R 12:27 5:28
/usr/bin/whois -h 1 knoop.nl

I accidentally placed a '1' for the forced server option (-h). When a
server is given that can not respond error handling is done properly.

I could reproduce it via the command line:

_[root@s01.knoop.nl ~]# whois -h 1 *_querydomain.nl
*
[Querying 1]
^C

  •       ( => needed to manually abort!!) *_[root@s01.knoop.nl
    
    ~]# whois -h a.nl *_querydomain.nl
    *
    [Querying a.nl]
    [a.nl: Name or service not known]
    [Unable to connect to remote host]
    *[root@s01.knoop.nl ~]# whois -h knoop.nl
    querydomain.nl *
    [Querying knoop.nl]
    [Unable to connect to remote host]
    *[root@s01.knoop.nl ~]# whois querydomain.nl
    *
    [Querying whois.domain-registry.nl]
    [whois.domain-registry.nl]
    querydomain.nl is free

*[root@s01.knoop.nl ~]# whois *jwhois version 4.0,
Copyright (C) 1999-2007 Free Software Foundation, Inc.
This program is free software with ABSOLUTELY NO WARRANTY; you may
redistribute it under the terms of the GNU General Public License.

Usage: jwhois [OPTIONS] [QUERY]
--version display version number and patch level
--help display this help
-v, --verbose verbose debug output
-c FILE, --config=FILE use FILE as configuration file
-h HOST, --host=HOST explicitly query HOST
-n, --no-redirect disable content redirection
-s, --no-whoisservers disable whois-servers.net service support
-a, --raw disable reformatting of the query
-i, --display-redirections display all redirects instead of hiding them
-p PORT, --port=PORT use port number PORT (in conjunction with HOST)
-r, --rwhois force an rwhois query to be made
--rwhois-display=DISPLAY sets the display option in rwhois queries
--rwhois-limit=LIMIT sets the maximum number of matches to return

Report bugs to bug-jwhois@gnu.org
[root@s01.knoop.nl ~]#

If you need further assitance/information, please contact me.



via Email http://ift.tt/14sBgXq

January 08, 2015 at 09:21AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant