See connection's tcp timers Show Sample Output
Short list of all ip. Shows even the newly supported multiple ip address on the same interface (see eth1). For ipv6 use -6 Show Sample Output
Dump 389ds schema, putting "\n " on one line with perl. You have to specify the objectclasses, attributetypes operational attributes too, otherwise they won't be dumped!
This should work with different locales. Another post reports Show Sample Output
Get info directly from /proc/uptime
faster ;) but your idea is really cool
No need for further filedes or substitution for splitting. Simply use read a b
avoid wc overload ;)
don't need echo :P
use -iname \*[.ch] instead of -iname \*.c -o -iname \*.h
use Linux ;) Show Sample Output
note the xargs at the end
and you quickly know the files you changed Show Sample Output
default stack size is 10M. This makes your multithread app filling rapidly your memory. on my PC I was able to create only 300thread with default stack size. Lower the default stack size to the one effectively used by your threads, let you create more. ex. putting 64k I was able to create more than 10.000threads. Obviously ...your thread shouldn't need more than 64k ram!!!
grep -o puts each occurrence in a separate line
Don't track in history commands starting with whitespace. Moreover ignore duplicates from history. To be set in .bashrc ex. $ export HISTCONTROL=ignoreboth $ echo antani $ history|grep -c antani
greps using only ascii, skipping the overhead of matching UTF chars. Some stats: $ export LANG=C; time grep -c Quit /var/log/mysqld.log 7432 real 0m0.191s user 0m0.112s sys 0m0.079s $ export LANG=en_US.UTF-8; time grep -c Quit /var/log/mysqld.log 7432 real 0m13.462s user 0m9.485s sys 0m3.977s Try strace-ing grep with and without LANG=C
this is useful to highlight only some code without losing other lines (eg. software, logs, scripts)
using mb it's still readable;) a symbol variation $ du -ms {,.[^.]}* | sort -nk1 Show Sample Output
avoid rm to be recursive until you complete the command: put the -rf at the end!
commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.
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: