fix temporary file cleanup to properly handle filenames with spaces a… #20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nd special characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the temporary file cleanup in LinuxCleaner_42.sh used unquoted command substitution (clean_glob $(find /tmp ...)) which failed on filenames containing spaces or special characters due to improper word splitting
replaced with find -exec command which safely processes each file individually without relying on shell expansion
find /tmp -type f -user "$USER" -exec rm -f {} ; 2>/dev/null
ensures reliable cleanup of all temporary files regardless of filename complexity