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.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Find out current working directory of a process

Terminal - Find out current working directory of a process
eval ls -l /proc/{$(pgrep -d, COMMAND)}/cwd
2011-04-14 13:41:58
User: splante
Functions: eval ls
Find out current working directory of a process

This is an alternative to another command using two xargs. If it's a command you know there's only one of, you can just use:

ls -l /proc/$(pgrep COMMAND)/cwd


There is 1 alternative - vote for the best!

Terminal - Alternatives
echo "${0%/*}"
2011-04-17 12:09:56
User: mhs
Functions: echo

Invoked from within a shell script, this will print the directory in which the script resides. Doesn't depend on external tools, /proc/self/*, etc.. (`echo` is a shell builtin.) To see the *current working* directory of a script, use `pwd`.

echo COMMAND | xargs -ixxx ps -C xxx -o pid= | xargs -ixxx ls -l /proc/xxx/cwd
readlink /proc/self/cwd
mydir=$(cd $(dirname ${BASH_SOURCE:-$0});pwd)
2011-04-27 16:33:38
User: xeor
Functions: cd dirname
Tags: cd script pwd

I submitted a command like this without $0 if $BASH_SOURCE is unset. Therefor, it did only work when using ./script, not using 'sh script'. This version handles both, and will set $mydir in a script to the current working directory. It also works on linux, osx and probably bsd.

pwdx $(pgrep command)
2013-02-01 08:33:15
User: weidenrinde

The pwdx command reports the current working directory of a process or processes.

Know a better way?

If you can do better, submit your command here.

What others think

The above command didn't work for me. I need to add the double quotation to make it work

eval "ls -l /proc/{$(pgrep -d, bash)}/cwd"

Comment by sungam 288 weeks ago

Interesting. It works for me without the quotes on CentOS 5.5, bash v3.2.25(1) and OpenSUSE 11.4 bash v 4.1.10(1). It also worked on zsh 4.3.10 without quotes. What shell and version didn't it work on?

Comment by splante 288 weeks ago

eval is not needed. Just type 'ls -l /proc/$(pgrep -d, X)/cwd'

Comment by chmurli 287 weeks and 6 days ago

chmurli, your version works if there is one process running for the command, in which case you don't need the "-d," either. If you notice, I had mentioned that in the comments. If there is more than one process, you need the curly braces and the comma, and you need the eval.

Comment by splante 287 weeks and 4 days ago

Your point of view

You must be signed in to comment.