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:
Short list of all ip.
Shows even the newly supported multiple ip address on the same interface (see eth1).
For ipv6 use -6
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!
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!
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!
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!
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!
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!
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!
Just use find. No need to test file existence. On gnu find you can limit directory depth. Use "{}" to manage correctly files with spaces
No need for further filedes or substitution for splitting. Simply use read a b
use -iname \*[.ch] instead of -iname \*.c -o -iname \*.h
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!!!