I have my_script.sh in multiple directories.
How could I find it, then change directory there, and execute it, one by one?

../a/b c/d/my_script.sh
../e/f g/h/my_script.sh
....

find . -name 'my_script.sh' -exec (cd dirname of {} ; sh my_script.sh ) \;

I tried just echoing the dirname with no success ...
$ find . -name update_files_b0783.sh -exec echo ${{}%/*} \;
-bash: ${{}%/*}: bad substitution

Any help appreciated.
TIA

On 09.02.23 17:49, Harry wrote:
> I have my_script.sh in multiple directories.
> How could I find it, then change directory there, and execute it, one by one?
>
> ./a/b c/d/my_script.sh
> ./e/f g/h/my_script.sh
> ...
>
> find . -name 'my_script.sh' -exec (cd dirname of {} ; sh my_script.sh ) \;
>
> I tried just echoing the dirname with no success ...
> $ find . -name update_files_b0783.sh -exec echo ${{}%/*} \;
> -bash: ${{}%/*}: bad substitution

My pragmatic solution: Whip up a script:
#! /bin/bash
dir="${1%/*}"
script="${1##*/}"
cd "$dir" && sh "$script"

Then use the script(name) as the argument to "-exec"

Josef

On Thu, 09 Feb 2023 08:49:58 -0800, Harry wrote:

> I have my_script.sh in multiple directories.
> How could I find it, then change directory there, and execute it, one by
> one?
>
> ./a/b c/d/my_script.sh ./e/f g/h/my_script.sh ...
>
> find . -name 'my_script.sh' -exec (cd dirname of {} ; sh my_script.sh )
> \;

How about
find . -name 'my_script.sh' -print | while read SP ; do "$SP" ; done

--
Lew Pitcher
"In Skills We Trust"

On Thursday, February 9, 2023 at 9:13:03 AM UTC-8, Josef Möllers wrote:

> My pragmatic solution: Whip up a script:
> #! /bin/bash
> dir="${1%/*}"
> script="${1##*/}"
> cd "$dir" && sh "$script"
>
> Then use the script(name) as the argument to "-exec"

Josef,
It only went through one of the many directories.

On Thursday, February 9, 2023 at 9:30:51 AM UTC-8, Lew Pitcher wrote:

> How about
> find . -name 'my_script.sh' -print | while read SP ; do "$SP" ; done

Lew
I haven't tried your suggestion yet ...
It has to "cd <the destination directory>" first, because my_script.sh would try to copy files from some_directory to those already existing in <the destination directory>.

On 09.02.2023 19:15, Harry wrote:
> On Thursday, February 9, 2023 at 9:13:03 AM UTC-8, Josef Möllers wrote:
>
>> My pragmatic solution: Whip up a script:
>> #! /bin/bash
>> dir="${1%/*}"
>> script="${1##*/}"
>> cd "$dir" && sh "$script"
>>
>> Then use the script(name) as the argument to "-exec"
>
> Josef,
> It only went through one of the many directories.
>

What if you expand the loop in shell...?

find -name "my_script.sh" |
while read f ; do ( cd "${f%/*}" && sh "${f##*/}" ) ; done

But note that you need adjustments for pathological filenames.

Also it might be worth a thought in case it's possible that
malicious files in the directory hierarchy might be executed.

Janis

On Thu, 09 Feb 2023 10:19:59 -0800, Harry wrote:

> On Thursday, February 9, 2023 at 9:30:51 AM UTC-8, Lew Pitcher wrote:
>
>> How about find . -name 'my_script.sh' -print | while read SP ; do "$SP"
>> ; done
>
> Lew I haven't tried your suggestion yet ...
> It has to "cd <the destination directory>" first, because my_script.sh
> would try to copy files from some_directory to those already existing in
> <the destination directory>.

That's fair. My suggestion doesn't do that.

--
Lew Pitcher
"In Skills We Trust"

On Thursday, February 9, 2023 at 10:21:57 AM UTC-8, Janis Papanagnou wrote:

> What if you expand the loop in shell...?
>
> find -name "my_script.sh" |
> while read f ; do ( cd "${f%/*}" && sh "${f##*/}" ) ; done
>
> But note that you need adjustments for pathological filenames.
>
> Also it might be worth a thought in case it's possible that
> malicious files in the directory hierarchy might be executed.
>
> Janis

Janis

It works.
Thanks a lot for your help.

H.