Failed to execute child

Hej Endeavour people

I want to run a program using terminal, the program or Shell (I think) is VASSAL.sh using Terminal Emulator, but the only thing I get is → Failed to execute child - How do I fix this?

Ulrik

The file probably needs proper rights to run as root? I’m not very well versed on this subject but that’s my guess. :thinking:

The program already have : Allow this file to run as a program

That doesn’t necessarily mean it has the right privileges. Most scripts you down load need to have permissions to run as root using the following as far as i know. :thinking: I’m not an expert on using scripts or creating them. :wink:

chmod +x script.sh
./script.sh

1 Like

WOW it worked

Thanks ricklinux, you are the man :star_struck:

1 Like

FWIW, I think executing children is criminal…

8 Likes

At a minimum it’s the root of evil.

1 Like

Ya we should only use chmod! :wink:

Edit: And when they don’t comply? … +x :rofl:

1 Like

Hej Ricklinux

maybe you can help me once again

The two commands still work, but I have to write them every time I run the script

Is there a way to fix this too?

Ulrik

You shouldn’t have to as far as I know? I’m not well versed with scripts so maybe someone else can answer that?

I’m not fully understanding what you want to do. So, do you want to create a new script that executes the other scripts?
Or create a .desktop file (a launcher that runs your scripts) that you can simply click with a mouse?
Or something else?

I think i understand but I’m not sure. The OP downloaded a script and tried to run it but got the error failed to execute child. I told the OP it probably didn’t have the right root privileges. So i said to run the commnds i gave and that worked.

chmod +x *script*.sh
./*script*.sh

It would seem that the OP wants to run this script repeatedly or again for some reason but has to use the chmod commands each time. I’m not very versed on chmod and scripts. I assume it’s still related to user privileges that have root access? Maybe I’m totally out to lunch here. :laughing:

Looks like the user opened another topic for this issue.

Edit: I’ll close this one now then.