Hide

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.

OpenID
or
Sign in Register

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

Hide

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:

Hide

News

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.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

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
3
Up
Down
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.

Add to favourites | Report as malicious

Alternatives

There are 3 alternatives - 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
19
Up
Down
Find files that were modified by a given command

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

Show sample output | Comments (3) | Add to favourites | Report as malicious

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 193 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 193 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 193 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 193 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 193 weeks and 5 days ago

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

Comment by bwoodacre 193 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts