perl script to find all files with certain extensions

Hi

Try it with double quotes.

find /opt/lampp/htdocs/ -name "*" -path "/opt/lampp/htdocs/some/folder" -prune -o -path "/opt/lampp/htdocs/another/folder" -prune -o -print;

If that fails, escape the double quotes

find /opt/lampp/htdocs/ -name \"*\" -path \"/opt/lampp/htdocs/some/folder\" -prune -o -path \"/opt/lampp/htdocs/another/folder\" -prune -o -print;

I hope that helps

Awesome that did help. It now executes!

Do you know about part 2?

Also it includes directories as well... can I exclude those from the results?

You don't need -name if you want all files.

I think the simplest thing to do since you say it's in a perl script is to do the find in perl rather than using the find command.  This should do what you want...

#!/usr/bin/perl
    eval 'exec /usr/bin/perl -S $0 ${1+"$@"}'
        if 0; #$running_under_some_shell

use strict;
use warnings;
use File::Find ();

# Set the variable $File::Find::dont_use_nlink if you're using AFS,
# since AFS cheats.

# for the convenience of &wanted calls, including -eval statements:
use vars qw/*name *dir *prune/;
*name   = *File::Find::name;
*dir    = *File::Find::dir;
*prune  = *File::Find::prune;

sub wanted {
    #my ($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_);
    if ($name =~ /^\/opt\/lampp\/htdocs\/some\/folder\z/s or
        $name =~ /^\/opt\/lampp\/htdocs\/another\/folder\z/s) {
    	$prune = 1
    } elsif ($name =~ /\.(?:pl|txt|php|html|xml|js)$/) {
        print "$name\n";
    }
}


# Traverse desired filesystems
File::Find::find({wanted => \&wanted}, '/opt/lampp/htdocs');

Select allOpen in new window

To only include files in find, you can do -type f.

Hmm so I have ...

find /opt/lampp/htdocs/ -name \"*.php\" -o -name \"*.js\" -o -name \"*.html\" -o -name \"*.pl\" -o -name \"*.xml\" -o -name \"*.txt\" -path \"/opt/lampp/htdocs/some/folder\" -prune -o -path \"/opt/lampp/htdocs/another/folder\" -prune -o -print;

That seemed to cut down my results from almost 10000 to about 6000 but I am still seeing lots of image files and pdf's and also the directories.

Just use grep to remove the last results:

find /opt/lampp/htdocs/ -name \"*.php\" -o -name \"*.js\" -o -name \"*.html\" -o -name \"*.pl\" -o -name \"*.xml\" -o -name \"*.txt\" -path \"/opt/lampp/htdocs/some/folder\" -prune -o -path \"/opt/lampp/htdocs/another/folder\" -prune -o -print | grep -v \".unwanted\" | grep -v \".moreunwanted\"

Did you look at the perl solution I posted?  For complex finds, I find it much simpler to write it in perl where it can be much clearer what is going on and much easier to modify it (add more file types to include dirs to exclude, etc).

This is correct usage for multiple patterns.
find . -type f \( -name \"*.java\" -o -name \"*.xml\" -o -name \"*.html\" \)

Yep, sorry I did, but was trying the other suggestions. The script I have already uses a lot of the find commands already so it would be preferable to stick with that... even though this command is just getting longer.

Does that perl find script of yours allow you to search on different systems as I am ssh ing to other boxes to do searches as well as the local one.... just to complicate things :/

So I now have

$command = "find /opt/lampp/htdocs/ -type f -o \( -name \"*.php\" -o -name \"*.js\" -o -name \"*.html\" -o -name \"*.pl\" -o -name \"*.xml\" -o -name \"*.txt\" \) -o -path '/opt/lampp/htdocs/some/folder' -prune -o -path '/opt/lampp/htdocs/another/folder/' -prune -o -print;";

Which I feel is pretty close... except I am getting this error when run

syntax error near unexpected token `('

i've tried
with and without the -o after the -find f
with and without the -o after the end bracket
with and without the slashes for the brackets...

Little confused :S

Sorry that error line is incomplete

bash: -c: line 0: syntax error near unexpected token `('

OK, brackets wont work.
Sorry.

Try escaping the  * too.
-name \"\*.php\"

Oh you know what... its actually now doing the opposite of what I want... so its excluding all the file types I want and returning the ones I dont

$command = "find /opt/lampp/htdocs/ -type f -name \"*.php\" -o -name \"*.js\" -o -name \"*.html\" -o -name \"*.pl\" -o -name \"*.xml\" -o -name \"*.txt\" -path '/opt/lampp/htdocs/some/folder' -prune -o -path '/opt/lampp/htdocs/another/folder/' -prune -o -print;";

Hmm this command didnt work BitFreeze

print $command = "find /opt/lampp/htdocs/ -type f -name \"*.php\" -o -name \"*.js\" -o -name \"*.html\" -o -name \"*.pl\" -o -name \"*.xml\" -o -name \"*.txt\" -path '/opt/lampp/htdocs/some/folder/' -prune -o -path '/opt/lampp/htdocs/another/folder' -prune -o -print | grep -v \"*.png\" | grep -v \"*.jpg\";";

Hi Everyone

Thanks for all your suggestions...

With the help of a colleague I have found a solution

$command = "find /opt/lampp/htdocs -nowarn -path \"*directory_1*\" -prune -o -path \"*Directory_2*\" -prune -o -regextype posix-awk -regex \"(.*.html|.*.js|.*.pl|.*.php|.*.txt|.*.xml)\" -type f -print";

The regextype list can be used to add whatever files I actually require.

The prune path needs to be at the front of the command or it breaks everything.

The -nowarn is needed because the way the command works it gives a warning message at the start even though it works perfectly.

This did take a while to work out... you wouldn't think it would be that hard. The prune is very finicky and if you use it in the wrong place it completely destroys your command which I think is the hardest part of this problem.

-or does the same thing.

Hi Vee Mod

I closed this and awarded points and it appears to me to have done the same thing. It looks like I have not awarded points to the experts but I have.

Cheers

Snarfles

Objecting on behalf of author.

Snarfles: Please let us know which comments you'd like to accept and the number of points you'd like to award to each and we'll manage this for you. EE is making changes to the closure process and there are still some glitches to work out.

SouthMod
Community Support Moderator

Hey, I'm actually traveling atm so bit hard to make comments, but the comments you selected as answers were close to what I was going to select anyway so thanks for closing this.
Cheers