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/
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.
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
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:
Returns logs between HH:M[Mx-My], for example, between 13:40 and 13:45.
There are 7 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
That kind of things cannot be easily adapted to grep range of minutes like : 39-45.
Depending on your input, the use of awk may be a wise choice.
Backticks are more harm than good. Learn the way of the Jedi:
grep -i "$(date +%b" "%d" ")13:4[0-5]" syslogbe carefull because sometimes you may have date inside log messages, for example :
Nov 23 13:53:16 my_mx postfix/scache[29106]: statistics: start interval Nov 23 13:43:16
so try this :
grep -i ^"$(date +%b" "%d" ")13:4[0-5]" syslog