find builtin in bash v4+

ls -l /etc/**/*killall
This command will give you the same list of files as "find /etc/ -name '*killall' | xargs ls -l". In a simpler format just do 'ls /etc/**/file'. It uses shell globbing, so it will also work with other commands, like "cp /etc/**/sshd sshd_backup".
Sample Output
[root@localhost ~]# ls -l /etc/**/*killall
-rwxr-xr-x. 1 root root 652 Apr 19 15:47 /etc/init.d/killall
lrwxrwxrwx. 1 root root  17 May 31 06:00 /etc/rc0.d/S00killall -> ../init.d/killall
lrwxrwxrwx. 1 root root  17 May 31 06:00 /etc/rc6.d/S00killall -> ../init.d/killall

9
By: xeor
2011-08-30 05:57:49

These Might Interest You

  • don't `man bash` Show Sample Output


    -4
    help builtin
    kev · 2011-12-25 04:52:49 2
  • I just found another use for the builtin ':' bash command. It increments counters for me in a loop if a certain condition is met... : [arguments] No effect; the command does nothing beyond expanding arguments and performing any specified redirections. A zero exit code is returned. Show Sample Output


    2
    [ $V ] || : $((V++)) && echo $V
    axelabs · 2012-06-15 16:48:03 0
  • Similar to xargs -i, but works with builtin bash commands (rather than running "bash -c ..." through xargs)


    3
    xargsb() { while read -r cmd; do ${@//'{}'/$cmd}; done; }
    BobbyTables · 2010-09-28 06:35:39 3
  • The "type" builtin command is handy to find out what executable will be used if you issue a command. But on some distros, particularly when using /etc/alternatives, certain executables get buried under layers and layers of symbolic links and it becomes hard to find which one. If you put the above command in your .bashrc, it adds a "-c" option to the type command that will weed through the symbolic links and prints the actual file that will be executed. Show Sample Output


    0
    type () { if [ "$1" = "-c" ]; then shift; for f in "$@"; do ff=$(builtin type -p "$f"); readlink -f "$ff"; done; else builtin type $typeopts "$@"; fi; }
    splante · 2011-04-07 18:57:51 0

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

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.

Share Your Commands



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: