find: paths must precede expression: iname

Entropy1024 · 03-13-2018, 10:37 AM

I'm attempting to search a folder for files named sample.avi, sample.mp4 & sample.mkv that are under 40Meg in size and delete them.

I have trued the bit of code below but it results in an "find: paths must precede expression: iname" error.

Code:

find /home/Videos/ -type f \( -iname \sample.avi -o iname \sample.mp4 -o iname \sample.mkv\) -size -40M -delete

Where am I going wrong?

Cheers

Entropy1024 · 03-13-2018, 11:30 AM

Quote:

Originally Posted by Entropy1024

I'm attempting to search a folder for files named sample.avi, sample.mp4 & sample.mkv that are under 40Meg in size and delete them.

I have trued the bit of code below but it results in an "find: paths must precede expression: iname" error.

Code:

find /home/Videos/ -type f \( -iname \sample.avi -o iname \sample.mp4 -o iname \sample.mkv\) -size -40M -delete

Where am I going wrong?

Cheers

Sorry I just figured it out. Was missing a - before the inames

Sefyir · 03-13-2018, 11:31 AM

Quote:

Originally Posted by Entropy1024

I'm attempting to search a folder for files named sample.avi, sample.mp4 & sample.mkv that are under 40Meg in size and delete them.

I have trued the bit of code below but it results in an "find: paths must precede expression: iname" error.

Code:

find /home/Videos/ -type f \( -iname \sample.avi -o iname \sample.mp4 -o iname \sample.mkv\) -size -40M -delete

Where am I going wrong?

Cheers

I've bolded and then bracketed the changes I made.
The second one is invalid (because of the brackets)
Essentially, when using -o, it means or. So you still need to include the - before iname (-o -iname, not -o iname)
Also, \sample.avi doesn't mean much. It's typically used with \*sample.avi to wildcard match everything before sample.avi. If you're not using something the shell will expand, the \ is not needed

Once you've validated that it is working, then put the -delete back in. Never use -delete until you're positive you're going to get the results you want (which is not true until you get your command working)

Code:

find /home/Videos/ -type f \( -iname \*sample.avi -o -iname \*sample.mp4 -o -iname \*sample.mkv \) -size -40M

Code:

find /home/Videos/ -type f \( -iname \[*]sample.avi -o [-]iname \[*]sample.mp4 -o [-]iname \[*]sample.mkv[ ]\) -size -40M

BW-userx · 03-13-2018, 01:35 PM

I don't even use the escapes,

Code:

find /path -type f -iname "*dh.jpg" -o -iname "*.jpg"

rknichols · 03-13-2018, 05:05 PM

Quote:

Originally Posted by BW-userx

I don't even use the escapes,

Code:

find /path -type f -iname "*dh.jpg" -o -iname "*.jpg"

That has the implied binding

Code:

find /path \( -type f -iname "*dh.jpg" \) -o -iname "*.jpg"

A name matching that final '-iname "*.jpg"' does not have to pass the '-type f' test. It "works" for you since you probably don't have anything but ordinary files with that extension.

BW-userx · 03-13-2018, 05:33 PM

well I'm not one to name my directories like files with an extension if that is what you mean.

that what I used was just a quick example,
here off one of my scripts, depending on my needs at the moment.

Code:

done <<<"$(find "$working_dir"   -type f -name "*.mp3" -o -name "*.Mp3" -o -name "*.MP3" -o -name "*.flac" )"
#done <<<"$(find "$working_dir"  "$working_dir2"  -type f -name "*.mp3" -o -name "*.Mp3" -o -name "*.MP3" -o -name "*.flac" )"
#done <<<"$(find "$working_dir" -not \( -path /media/data/deluge-download -prune \) -type f -name "*.mp3" -o -name "*.Mp3" -o -name "*.MP3" -o -name "*.flac" )"

rknichols · 03-13-2018, 08:12 PM

Quote:

Originally Posted by BW-userx

Code:

done <<<"$(find "$working_dir"   -type f -name "*.mp3" -o -name "*.Mp3" -o -name "*.MP3" -o -name "*.flac" )"
#done <<<"$(find "$working_dir"  "$working_dir2"  -type f -name "*.mp3" -o -name "*.Mp3" -o -name "*.MP3" -o -name "*.flac" )"
#done <<<"$(find "$working_dir" -not \( -path /media/data/deluge-download -prune \) -type f -name "*.mp3" -o -name "*.Mp3" -o -name "*.MP3" -o -name "*.flac" )"

Those all share the same problem. You might as well leave out the "-type f" test since the result is not being used for any of the matches following that first "-o". If you don't believe that, try changing it to "-type s" (socket) and see the result. The "*.mp3" names will be excluded since they are not sockets, but all of the other "or" terms in that expression will still be found.

BW-userx · 03-13-2018, 08:14 PM

Quote:

Originally Posted by rknichols

Those all share the same problem. You might as well leave out the "-type f" test since the result is not being used for any of the matches following that first "-o". If you don't believe that, try changing it to "-type s" (socket) and see the result. The "*.mp3" names will be excluded since they are not sockets, but all of the other "or" terms in that expression will still be found.

yeah you're prob right, its never caused me an issue. probably because I know my files.

but if you need to point fingers. then point fingers at the post I found showing me what I posted. that is where I learned it, by googling how to's.