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 files that were modified by a given command

Terminal - Find files that were modified by a given command
strace <name of the program>
2009-08-31 20:42:50
User: eitland
Functions: strace
Find files that were modified by a given command

Traces the system calls of a program. See http://linuxhelp.blogspot.com/2006/05/strace-very-powerful-troubleshooting.html for more information.


There is 1 alternative - vote for the best!

Terminal - Alternatives
touch /tmp/file ; $EXECUTECOMMAND ; find /path -newer /tmp/file
2009-08-31 18:47:19
User: matthewdavis
Functions: find touch

This has helped me numerous times trying to find either log files or tmp files that get created after execution of a command. And really eye opening as to how active a given process really is. Play around with -anewer, -cnewer & -newerXY

Know a better way?

If you can do better, submit your command here.

What others think

Although be warned strace catches extra junk such as linker activity and process setup even before the program you desire is exec'd.

Comment by bwoodacre 372 weeks and 6 days ago

Yeah, at least use "-e file" with it, or better yet look at something like "dpkg-depcheck" which actually interprets strace output specifically with this in mind...

Comment by eichin 372 weeks and 6 days ago

Advantage of the strace against t

touch /tmp/file ; $EXECUTECOMMAND ; find /path -newer /tmp/file

is that you don't have to wait for find.

Comment by eitland 372 weeks and 6 days ago

Surely the strace command is different from the touch-exec-find combo? The latter will find all files changed within a time window, meaning that they could have been modified by any other process. The strace command will ONLY show files modified by the specific process. Right?

Comment by sandman 372 weeks and 5 days ago

That is true, the touch-exec-find combo will find other files. But its useful for quick & dirty commands.

strace -ff |grep open

would probably suffice to truly find all files touched by a given command.

Comment by matthewdavis 372 weeks and 5 days ago

dpkg-depcheck is available in the 'devscripts' package, for those running debian/ubuntu.

Comment by bwoodacre 372 weeks and 5 days ago

Your point of view

You must be signed in to comment.