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.
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:
grabbed from Andrew Aylett post:
Avoids the nested 'find' commands but doesn't seem to run any faster than syssyphus's solution.
I used to do this sorting with:
sort file.txt | uniq -c | sort -nr
But this would cause the line (2nd column) to be sorted in descending (reverse) order as well sa the 1st column. So this will ensure the 2nd column is in ascending alphabetical order.
This is a modified version of the OP, wrapped into a bash function.
This version handles newlines and other whitespace correctly, the original has problems with the thankfully rare case of newlines in the file names.
It also allows checking an arbitrary number of directories against each other, which is nice when the directories that you think might have duplicates don't have a convenient common ancestor directory.
# find assumes email files start with a number 1-9
# sed joins the lines starting with " " to the previous line
# gawk print the received and from lines
# sort according to the second field (received+from)
# uniq print the duplicated filename
# a message is viewed as duplicate if it is received at the same time as another message, and from the same person.
The command was intended to be run under cron. If run in a terminal, mutt can be used:
mutt -e "push otD~=xq" -f $folder
count & sort one field of the log files , such as nginx/apache access log files .
#_connects src_IP dst_IP When_It_Happened_Secs
The following displays only the entries that are duplicates.
cut -f1,2 - IP range 16
cut -f1,2,3 - IP range 24
cut -f1,2,3,4 - IP range 24
Uses line-porcelain in git blame, which makes it easier to parse the output.
shows number of mysql bin log events (which are mysql server events) per minute, useful to check stress times postmortem
See the summary.
Per country GET report, based on access log. Easy to transform to unique IP
The listing will be nice separated with dashes in chunks of identical files.
Size Inode Mode Count_of_identical_files UID GID Date Time Path/Filename
find -printf "%f\n" prints just the file name from the given path. This means directory paths which contain extensions will not be considered.
depends on date format locale ...
useful to count events in logs
Detect duplicate UID in you /etc/passwd (or GID in /etc/group file).
Duplicate UID is often forbidden for it can be a security breach.