Very Computer

is there a quicker way (this is really slow)

Quote:> is there any quick way of finding all the executable scripts in a
> directory structure. I'm using the following find(1) command  :
>        find . -name SCCS -prune -o -follow -depth -exec file {} \;
> -print | \
>        grep executable|awk -F: '{print $1}'

> is there a quicker way (this is really slow)

find . -name SCCS -prune -o -follow -type f -exec file {} + |
  awk -F: '/executable/ {print $1}'

(note the "+" instead of ";" so that find runs as few file
instances as possible).

--
Stephane

Quote:> You may want to add  \( -perm -1 -o -perm -10 -o -perm -100 \)
> to the find rules

But shell scripts are not necessarily executables, they can be
called as: sh ./the-script.sh

--
Stephane

# /usr/bin/find /tmp -perm +111
find: -perm: Bad permission string
/usr/bin/find: path-list predicate-list

Even so, it looks to me like that would only match files will all three
execution bits set, not just one (as the previous one did).

Quote:> But shell scripts are not necessarily executables, they can be
> called as: sh ./the-script.sh

--

Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Quote:> (note the "+" instead of ";" so that find runs as few file
> instances as possible).

the + is interesting...mind explaining it further?  also, way back when,
i thought i saw a script use the {} for some sort of action...am i crazy
or not?

eg
find . -name SCCS -prune -o -follow -depth -exec file {Do Something in
Here} \;

i appreciate your time,
peter

Scripts can put commands in {} or () .

--
Elvis Notargiacomo  master AT barefaced DOT cheek
http://www.notatla.org.uk/goen/
    7.031: OnACPower returned value( 0x1 ) which is Equal To 0x1