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.




Checks apache's access_log file, strips the search queries and shoves them up your e-mail

Terminal - Checks apache's access_log file, strips the search queries and shoves them up your e-mail
cat /var/log/httpd/access_log | grep q= | awk '{print $11}' | awk -F 'q=' '{print $2}' | sed 's/+/ /g;s/%22/"/g;s/q=//' | cut -d "&" -f 1 | mail [email protected] -s "[your-site] search strings for `date`"
2009-11-22 03:03:06
User: isma
Functions: awk cat grep sed strings
Checks apache's access_log file, strips the search queries and shoves them up your e-mail

It's not a big line, and it *may not* work for everybody, I guess it depends on the detail of access_log configuration in your httpd.conf. I use it as a prerotate command for logrotate in httpd section so it executes before access_log rotation, everyday at midnight.


There is 1 alternative - vote for the best!

Terminal - Alternatives
awk '/q=/{print $11}' /var/log/httpd/access_log.4 | awk -F 'q=' '{print $2}' | sed 's/+/ /g;s/%22/"/g;s/q=//' | cut -d "&" -f 1
2009-11-22 17:13:48
User: isma
Functions: awk sed

as unixmonkey7109 pointed out, first awk parse replaces three steps.

Know a better way?

If you can do better, submit your command here.

What others think

useless use of cat, grep.

first 3 commands can be :

awk '/q=/{print $11}' /var/log/httpd/access_log.

I don't know how your log file looks like, but do you believe me if i say all the tools you use , grep, sed, cut etc can be done with just awk?

Comment by unixmonkey7109 279 weeks ago

Of course I believe you. I just didn't know better, thanks for your input. I didn't say it was perfect, or efficient, I just thought it could be useful to someone. I'll publish an alternative.

Comment by isma 278 weeks and 6 days ago

can you show a sample of your /var/log/httpd/access_log.4 file?

Comment by unixmonkey7109 278 weeks and 6 days ago

Your point of view

You must be signed in to comment.