this post was submitted on 06 Dec 2025
50 points (100.0% liked)

Linux

60185 readers
982 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
 

Hello everyone,

Hoping that this is a good place to post a question about Bash scripting. My wife and I have run into a problem in PhotoPrism where it keeps tagging pictures and videos with similar names together and so the thumbnail and the video do not match. I decided that rather than try to get her iPhone to tweak its naming it's easier to just offload to a directory then rename every file to a UUID before sending to photoprism. I'm trying to write a bash script to simplify this but cannot get the internal loop to fire. The issue appears to be with the 'while IFS= read -r -d '' file; do' portion. Is anyone able to spot what the issue may be?

#! /bin/bash
echo "This script will rename all files in this directory with unique names. Continue? (Y/N)"
read proceed
if [[ "$proceed" == "Y" ]]; then
	echo "Proceed"
	#use uuidgen -r to generate a random UUID.
	#Currently appears to be skipping the loop entirely. the find command works so issue should be after the pipe.
	   
# Troubleshooting
#Seems like changing IFS to $IFS helped. Now however it's also pulling others., don't think this is correct.
#verified that the find statement is correct, its the parsing afterwards that's wrong.
#tried removing the $'\0' after -d as that is string null in c. went to bash friendly '' based on https://stackoverflow.com/questions/57497365/what-does-the-bash-read-d-do
#issue definitely appears to be with the while statement
	find ./ -type f \( -iname \*.jpg -o -iname \*.png \) | while IFS= read -r -d '' file; do
	   echo "in loop"
	   echo "$file"
	   #useful post https://itsfoss.gitlab.io/post/how-to-find-and-rename-files-in-linux/
	   #extract the directory and filename
	   dir=$(dirname "$file")
	   base=$(basename "$file")
	   echo "'$dir'/'$base'"
	   #use UUID's to get around photoprism poor handling of matching file names and apples high collision rate
	   new_name="$dir/$(uuidgen -r)"
	   echo "Renaming ${file} to ${new_name}"
	   #mv "$file" "$new_name" #uncomment to actually perform the rename.
	done
	echo "After loop"
else
	echo "Cancelling"
fi

top 20 comments
sorted by: hot top controversial new old
[–] phaedrus@piefed.world 38 points 1 week ago* (last edited 1 week ago) (2 children)

You can do the entire thing as a one-liner using only find:

find ./ -type f \( -iname "*.jpg" -or -iname "*.png" \) -exec sh -c 'mv "$0" "$(uuidgen -r).${0##*.}"' {} \;  

Test on my machine:

phaedrus@sys76 ~/D/test> ls -lh  
total 0  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 test1.jpg  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 test1.png  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 test2.jpg  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 test2.png  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 test3.jpg  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 test3.png  
phaedrus@sys76 ~/D/test> find ./ -type f \( -iname "*.jpg" -or -iname "*.png" \) -exec sh -c 'mv "$0" "$(uuidgen -r).${0##*.}"' {} \;  
phaedrus@sys76 ~/D/test> ls -lh  
total 0  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 062d8954-9921-42bd-ad24-0e4ed403a5db.jpg  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 111f859f-b1fe-4488-b2bc-75585320e3a3.png  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 39b9fe4e-7a05-43c9-b30a-69e9a13aa3a9.png  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 57bda91e-49e5-43fe-8318-aeeb2e3adde7.png  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 97398eb7-54aa-488f-8fbe-0b84b5e5a50d.jpg  
-rw-r--r-- 1 phaedrus users 0 Dec  6 01:08 f7a13274-e2c0-4fa7-9907-c590d1280c2e.jpg  

btw, Lemmy doesn't like language specifiers in the multi-line code blocks, so it's difficult to read all that in its current form since there are no tabs to know how you have it formatted. Makes it virtually impossible to troubleshoot your specific script.

edit: further reading on the ever useful variable expansions (${0##*.} portion of my one-liner):
https://www.gnu.org/software/bash/manual/html_node/Shell-Parameter-Expansion.html

[–] BingBong@sh.itjust.works 19 points 1 week ago* (last edited 1 week ago) (2 children)

Interesting, the code shows up correctly for me in firefox. I wonder if that's due to my instance?

This works perfectly! Thank you!!! In case anyone else finds themselves wondering about the ${0##*.} portion, I found this article to be very helpful. https://stackoverflow.com/questions/30980062/0-and-0-in-sh

edit: You beat me to it with your link on parameter expansion. I'll be reading through that tonight as well. Thanks again.

[–] Badabinski@kbin.earth 5 points 1 week ago

If you want more help with Bash in the future, this is the best resource I've found in 13 years of writing bash professionally: https://mywiki.wooledge.org/EnglishFrontPage

Bash FAQs and pitfalls are the primary sections to look at there.

[–] phaedrus@piefed.world 5 points 1 week ago

It might be instance related, I'm on PieFed, so perhaps the markdown implementation is different.

Also, I realized that the parameter expansion might not be straightforward and added the GNU docs on it, but looks like you found a post about it at the same time! Glad to hear it got you sorted out.

[–] Badabinski@kbin.earth 4 points 1 week ago (1 children)

Thank you for providing the easiest and most portable answer. This will handle files with special characters perfectly unlike most of the responses here which rely on a while loop (to say nothing of a for loop ).

[–] phaedrus@piefed.world 1 points 1 week ago

Indeed, folks tend not to look into the docs enough to realize find is a powerful tool on its own!

I think the other answers were just adhering to the request (trying to troubleshoot the script as is), but I generally go for pragmatism despite not being what was actually requested.

[–] elmicha@feddit.org 4 points 1 week ago

You forgot the -print0 at the end of the find command. In the read -r -d '' you want to read NUL-separated strings, so you must tell the find command to also use NUL characters between the filenames.

[–] Rentlar@lemmy.ca 4 points 1 week ago* (last edited 1 week ago) (1 children)

Edit: I think there are better answers downthread than mine, but I hope my first comment spurned them on.

Not the most experienced bash guru at it but let me see...

  • does the while condition have to be within [ ] brackets?
  • Also I can't figure out what your condition is, it seems to have an unclosed quotation mark.
  • Most bash while-do-done loops I've made have a comparator like -ne for not equal or -le for less or equal to. So for example: while [ $variable -ne 5 ]; do
[–] FigMcLargeHuge@sh.itjust.works 3 points 1 week ago* (last edited 1 week ago)

Also, I am not sure you can automatically expect the output of the find command to be assigned to the file variable. I would output the find command to a temp file, and then grab the filenames one by one from the file and then put that in a do/done loop. Eg:

find ./ -type f \( -iname \*.jpg -o -iname \*.png \) > yourtempfile.tmp    
for file in `cat yourtempfile.tmp`     
do     
    echo "in loop"    
    echo "$file"    
....     
done

Here are some results I got when it ran:

in loop
./Figs_XSR900.JPG
'.'/'Figs_XSR900.JPG'
Renaming ./Figs_XSR900.JPG to ./356bb549-d25c-4c9b-a441-f8175f963c8c
in loop
./20240625195740_411A6199.JPG
'.'/'20240625195740_411A6199.JPG'
Renaming ./20240625195740_411A6199.JPG to ./3cc9ba51-1d15-4a10-b9ee-420a5666e3e2

[–] non_burglar@lemmy.world 3 points 1 week ago* (last edited 5 days ago)

Your find statement is not creating a variable "file" because it's missing the first part of the for loop. This:

find ./ -type f \( -iname \*.jpg -o -iname \*.png \) | while IFS= read -r -d '' file; do

should be this:

for file in "$(find ./ -type f \( -iname \*.jpg -o -iname \*.png \))"; do

However, the above command would find all files in current and subdirectories. You can just evaluate current context much more simply. I tested the below, it seems to work.

#! /bin/bash
echo "This script will rename all files in this directory with unique names. Continue? (Y/N)"
read proceed
if [[ "$proceed" == "Y" ]]; then
	echo "Proceed"
               for file in *.{jpg,JPG,png,PNG}; do
                    echo "in loop"
                    echo "$file"
                    dir=$(dirname "$file")
                    base=$(basename "$file")
                    echo "'$dir'/'$base'"
                    new_name="$dir/$(uuidgen -r)"
                    echo "Renaming ${file} to ${new_name}"
                    #mv "$file" "$new_name" #uncomment to actually perform the rename.
               done
	echo "After loop"
else
	echo "Cancelling"
fi

You could also find matching files first, evaluate if anything is found and add a condition to exit if no files are found.

Edit: who the fuck downvoted this, it literally works and the for loop was the issue.