What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.


Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.




Remove an IP address ban that has been errantly blacklisted by denyhosts

Terminal - Remove an IP address ban that has been errantly blacklisted by denyhosts
denyhosts-remove $IP_ADDRESS
2009-11-19 16:28:34
Remove an IP address ban that has been errantly blacklisted by denyhosts


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think


Sugsestion :

to initialize the BASE_PATH variable, you could extract it from the denyhosts.conf file

BASE_PATH=$(awk -F' = ' '$1 == "WORK_DIR" { print $2 }')
Comment by frans 262 weeks ago
Comment by frans 262 weeks ago

Apologize :

BASE_PATH=$(awk -F' = ' '$1 == "WORK_DIR" { print $2 }' /etc/denyhosts.conf)
Comment by frans 262 weeks ago

The script doesn't work with actual sh. It probably should start with


Comment by agladysh 258 weeks ago

It will be unfortunate for anyone who uses this script, as taking it out of /etc/hosts.deny is not enough. When they start the daemon back up, they'll notice the IP get blocked again. Probably best if you read the FAQ: http://denyhosts.sourceforge.net/faq.html#3_19.

You have 6 files to edit, before completely removing the IP address from denyhosts(8), and a 7th if you want to whitelist the IP.

Comment by atoponce 165 weeks and 6 days ago

ataponce, that's not what the script does. check out atrixnet.com for more details.

Comment by linuxrawkstar 165 weeks and 6 days ago

the script doesn't edit one file. take a look at the perl command in the script. it takes care of all the files it needs in order to really remove the lockout. thanks for your comments on the website.

Comment by linuxrawkstar 165 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts