We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System: fedora 35
Trying to run the script without +x execution permission using bash command. bash wait-for-it.sh google.com:80
bash wait-for-it.sh google.com:80
timeout: failed to run command ‘wait-for-it.sh’: No such file or directory wait-for-it.sh: timeout occurred after waiting 15 seconds for google.com:80
(The error message is same for above case even if execution permission is given)
But it works when directly executed given +x. ./wait-for-it.sh google.com:80
./wait-for-it.sh google.com:80
wait-for-it.sh: waiting 15 seconds for google.com:80 wait-for-it.sh: google.com:80 is available after 1 seconds
Any way I can use the script without giving it execution permission?
The text was updated successfully, but these errors were encountered:
It works when you give +x permissions and use ./ because that is the intended behavior by the system.
+x
./
Check the accepted answer for details: Why do I need to type ./ before executing a program in the current directory?
I don't think you can execute it without the required permission.
Sorry, something went wrong.
I get that, about the path issue. Turns out the script calls itself during execution, for that it needs the +x permission.
No branches or pull requests
System: fedora 35
Trying to run the script without +x execution permission using bash command.
bash wait-for-it.sh google.com:80
(The error message is same for above case even if execution permission is given)
But it works when directly executed given +x.
./wait-for-it.sh google.com:80
Any way I can use the script without giving it execution permission?
The text was updated successfully, but these errors were encountered: