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.

Universal configuration monitoring and system of record for IT.

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.

Top Tags



Find running binary executables that were not installed using dpkg

Terminal - Find running binary executables that were not installed using dpkg
cat /var/lib/dpkg/info/*.list > /tmp/listin ; ls /proc/*/exe |xargs -l readlink | grep -xvFf /tmp/listin; rm /tmp/listin
2009-09-09 18:09:14
User: kamathln
Functions: cat grep ls readlink rm xargs
Find running binary executables that were not installed using dpkg

This helped me find a botnet that had made into my system. Of course, this is not a foolproof or guarantied way to find all of them or even most of them. But it helped me find it.


There are 7 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Great command!

Comment by bwoodacre 293 weeks and 3 days ago

Really useful, thanks!

Comment by Patola 293 weeks and 2 days ago

This causes the ram memory to fill up on my machine. So I did this:

cat /var/lib/dpkg/info/*.list | egrep -v '\.(desktop|html|gz|xpm|png|jpg|svg|gif|css|xml|icon|glade|map|md5|tmpl|sample|h|c|rc|m4|mo|data2|ui)$' > /tmp/listin ; ls /proc/*/exe | xargs -l readlink | grep -xvFf /tmp/listin; rm /tmp/listin
Comment by Weboide 293 weeks and 1 day ago

Well, I just realized how not foolproof this is. There was one more botnet whose directory name was just a space. (yeah that one " ").

Can someone come up with a much better command (full input sanitization).

Comment by kamathln 293 weeks and 1 day ago

Never mind my previous comment. When I was trying out again, I had missed giving the '-l' option to xargs.

Weboide: please submit your command as an alternative

Comment by kamathln 293 weeks and 1 day ago

This works on Arch Linux:

ls /proc/*/exe | xargs -L1 readlink | while read line; do if ! pacman -Qo "$line" > /dev/null; then echo $line; fi;

Comment by matthewbauer 186 weeks and 6 days ago

Your point of view

You must be signed in to comment.