Don, is there a reason to not simply override IFS in read's environment? Also, I may be overly paranoid, but I use -r to defend against backslashes.

Code:

while IFS= read -r dir ...

Regards,
Alister

---------- Post updated at 12:29 PM ---------- Previous update was at 12:05 PM ----------

Because of -name . -prune not matching the current path, neither of those will work correctly.

A cd fixes the second suggestion:

Code:

while IFS= read -r d; do
(
    cd "$d" &&
    find . -type d ! -name . -prune -o -mtime +$Num_days -name '*.csv' -exec rm {} \;
)
done < dirlist.txt

If the paths are absolute, the subshell isn't needed.

An unwieldy solution that doesn't cd:

Code:

while IFS= read -r d; do
    find "$d" -type d \( -name "${d##*/}" -exec test "$d" = {} \; -o -prune \) -o -mtime +$Num_days -name '*.csv' -exec rm {} \;
done < dirlist.txt

For find implementations which support a -maxdepth primary (GNU, *BSD, etc) which simplifies restricting the traversal:

Code:

while IFS= read -r d; do
    find "$d" -maxdepth 1 -mtime +$Num_days -name '*.csv' -exec rm {} \;
done < dirlist.txt

Regards,
Alister