Executable file named 'test' is in $PATH but won't run












11















I have a file in $HOME/bin (before you ask, yes, it is in my path) called test which I've confirmed can be executed fine when I run it with the full path to the file. However, I get a really weird issue when I don't run it this way. When I just run test in the terminal, it doesn't do anything and returns immediately. I know that this isn't an issue of finding the file for several reasons:




  1. There is no error message. Normally if the file can't be found or can't be executed a message will be printed out saying so.


  2. Running which test still returns the correct file path.


  3. Probably the weirdest of all - the script works fine when run through strace. I tried using strace to see if I could figure out what was going on but when I ran it with strace, it worked as expected with 0 issues.







bash shell-script path executable strace







share|improve this question









New contributor




ContronThePanda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 7





    Use type, not which. See Why not use “which”? What to use then?

    – wjandrea
    yesterday













  • First tip at wiki-dev.bash-hackers.org/scripting/debuggingtips

    – Mark Wagner
    5 hours ago
















11















I have a file in $HOME/bin (before you ask, yes, it is in my path) called test which I've confirmed can be executed fine when I run it with the full path to the file. However, I get a really weird issue when I don't run it this way. When I just run test in the terminal, it doesn't do anything and returns immediately. I know that this isn't an issue of finding the file for several reasons:




  1. There is no error message. Normally if the file can't be found or can't be executed a message will be printed out saying so.


  2. Running which test still returns the correct file path.


  3. Probably the weirdest of all - the script works fine when run through strace. I tried using strace to see if I could figure out what was going on but when I ran it with strace, it worked as expected with 0 issues.







bash shell-script path executable strace







share|improve this question









New contributor




ContronThePanda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 7





    Use type, not which. See Why not use “which”? What to use then?

    – wjandrea
    yesterday













  • First tip at wiki-dev.bash-hackers.org/scripting/debuggingtips

    – Mark Wagner
    5 hours ago














11












11








11


1






I have a file in $HOME/bin (before you ask, yes, it is in my path) called test which I've confirmed can be executed fine when I run it with the full path to the file. However, I get a really weird issue when I don't run it this way. When I just run test in the terminal, it doesn't do anything and returns immediately. I know that this isn't an issue of finding the file for several reasons:




  1. There is no error message. Normally if the file can't be found or can't be executed a message will be printed out saying so.


  2. Running which test still returns the correct file path.


  3. Probably the weirdest of all - the script works fine when run through strace. I tried using strace to see if I could figure out what was going on but when I ran it with strace, it worked as expected with 0 issues.







bash shell-script path executable strace







share|improve this question









New contributor




ContronThePanda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I have a file in $HOME/bin (before you ask, yes, it is in my path) called test which I've confirmed can be executed fine when I run it with the full path to the file. However, I get a really weird issue when I don't run it this way. When I just run test in the terminal, it doesn't do anything and returns immediately. I know that this isn't an issue of finding the file for several reasons:




  1. There is no error message. Normally if the file can't be found or can't be executed a message will be printed out saying so.


  2. Running which test still returns the correct file path.


  3. Probably the weirdest of all - the script works fine when run through strace. I tried using strace to see if I could figure out what was going on but when I ran it with strace, it worked as expected with 0 issues.







bash shell-script path executable strace




bash shell-script path executable strace






share|improve this question









New contributor




ContronThePanda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




ContronThePanda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 3 hours ago









ivan_pozdeev

36619




36619






New contributor




ContronThePanda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked yesterday









ContronThePandaContronThePanda

563




563




New contributor




ContronThePanda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





ContronThePanda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






ContronThePanda is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 7





    Use type, not which. See Why not use “which”? What to use then?

    – wjandrea
    yesterday













  • First tip at wiki-dev.bash-hackers.org/scripting/debuggingtips

    – Mark Wagner
    5 hours ago














  • 7





    Use type, not which. See Why not use “which”? What to use then?

    – wjandrea
    yesterday













  • First tip at wiki-dev.bash-hackers.org/scripting/debuggingtips

    – Mark Wagner
    5 hours ago








7




7





Use type, not which. See Why not use “which”? What to use then?

– wjandrea
yesterday







Use type, not which. See Why not use “which”? What to use then?

– wjandrea
yesterday















First tip at wiki-dev.bash-hackers.org/scripting/debuggingtips

– Mark Wagner
5 hours ago





First tip at wiki-dev.bash-hackers.org/scripting/debuggingtips

– Mark Wagner
5 hours ago










1 Answer
1






active

oldest

votes


















41














test is an unfortunate name to use, it's the standard utility for conditional tests. (It's actually the same command as the [ in if [ ... ], it just looks like a syntactical thing, but is really just a normal command.)



test is also builtin in e.g. Bash, so running just test never looks up your binary from the path.



bash$ help test | head

test: test [expr]

    Evaluate conditional expression.



    Exits with a status of 0 (true) or 1 (false) depending on

    the evaluation of EXPR.  Expressions may be unary or binary.  

    [...]


test with no arguments just returns 1 (false).



Running strace test doesn't involve the shell builtin, since strace doesn't implement any utilities itself. It just uses what it finds in your PATH. Note that you probably have the standard test in /bin/test or /usr/bin/test, so if that would be first in PATH, strace would run run that.



On my Bash, which is also an external command, so it doesn't have an idea about builtins either. On the other hand, the type command is builtin to the shell, and type test would show that test is a shell builtin.



See also: Why not use "which"? What to use then?






share|improve this answer





















  • 10





    Have an anecdote from 1985.

    – JdeBP
    yesterday











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






ContronThePanda is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498685%2fexecutable-file-named-test-is-in-path-but-wont-run%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









41














test is an unfortunate name to use, it's the standard utility for conditional tests. (It's actually the same command as the [ in if [ ... ], it just looks like a syntactical thing, but is really just a normal command.)



test is also builtin in e.g. Bash, so running just test never looks up your binary from the path.



bash$ help test | head

test: test [expr]

    Evaluate conditional expression.



    Exits with a status of 0 (true) or 1 (false) depending on

    the evaluation of EXPR.  Expressions may be unary or binary.  

    [...]


test with no arguments just returns 1 (false).



Running strace test doesn't involve the shell builtin, since strace doesn't implement any utilities itself. It just uses what it finds in your PATH. Note that you probably have the standard test in /bin/test or /usr/bin/test, so if that would be first in PATH, strace would run run that.



On my Bash, which is also an external command, so it doesn't have an idea about builtins either. On the other hand, the type command is builtin to the shell, and type test would show that test is a shell builtin.



See also: Why not use "which"? What to use then?






share|improve this answer





















  • 10





    Have an anecdote from 1985.

    – JdeBP
    yesterday
















41














test is an unfortunate name to use, it's the standard utility for conditional tests. (It's actually the same command as the [ in if [ ... ], it just looks like a syntactical thing, but is really just a normal command.)



test is also builtin in e.g. Bash, so running just test never looks up your binary from the path.



bash$ help test | head

test: test [expr]

    Evaluate conditional expression.



    Exits with a status of 0 (true) or 1 (false) depending on

    the evaluation of EXPR.  Expressions may be unary or binary.  

    [...]


test with no arguments just returns 1 (false).



Running strace test doesn't involve the shell builtin, since strace doesn't implement any utilities itself. It just uses what it finds in your PATH. Note that you probably have the standard test in /bin/test or /usr/bin/test, so if that would be first in PATH, strace would run run that.



On my Bash, which is also an external command, so it doesn't have an idea about builtins either. On the other hand, the type command is builtin to the shell, and type test would show that test is a shell builtin.



See also: Why not use "which"? What to use then?






share|improve this answer





















  • 10





    Have an anecdote from 1985.

    – JdeBP
    yesterday














41












41








41







test is an unfortunate name to use, it's the standard utility for conditional tests. (It's actually the same command as the [ in if [ ... ], it just looks like a syntactical thing, but is really just a normal command.)



test is also builtin in e.g. Bash, so running just test never looks up your binary from the path.



bash$ help test | head

test: test [expr]

    Evaluate conditional expression.



    Exits with a status of 0 (true) or 1 (false) depending on

    the evaluation of EXPR.  Expressions may be unary or binary.  

    [...]


test with no arguments just returns 1 (false).



Running strace test doesn't involve the shell builtin, since strace doesn't implement any utilities itself. It just uses what it finds in your PATH. Note that you probably have the standard test in /bin/test or /usr/bin/test, so if that would be first in PATH, strace would run run that.



On my Bash, which is also an external command, so it doesn't have an idea about builtins either. On the other hand, the type command is builtin to the shell, and type test would show that test is a shell builtin.



See also: Why not use "which"? What to use then?






share|improve this answer















test is an unfortunate name to use, it's the standard utility for conditional tests. (It's actually the same command as the [ in if [ ... ], it just looks like a syntactical thing, but is really just a normal command.)



test is also builtin in e.g. Bash, so running just test never looks up your binary from the path.



bash$ help test | head

test: test [expr]

    Evaluate conditional expression.



    Exits with a status of 0 (true) or 1 (false) depending on

    the evaluation of EXPR.  Expressions may be unary or binary.  

    [...]


test with no arguments just returns 1 (false).



Running strace test doesn't involve the shell builtin, since strace doesn't implement any utilities itself. It just uses what it finds in your PATH. Note that you probably have the standard test in /bin/test or /usr/bin/test, so if that would be first in PATH, strace would run run that.



On my Bash, which is also an external command, so it doesn't have an idea about builtins either. On the other hand, the type command is builtin to the shell, and type test would show that test is a shell builtin.



See also: Why not use "which"? What to use then?







share|improve this answer














share|improve this answer



share|improve this answer








edited 19 hours ago

























answered yesterday









ilkkachuilkkachu

58.1k889164




58.1k889164








  • 10





    Have an anecdote from 1985.

    – JdeBP
    yesterday














  • 10





    Have an anecdote from 1985.

    – JdeBP
    yesterday








10




10





Have an anecdote from 1985.

– JdeBP
yesterday





Have an anecdote from 1985.

– JdeBP
yesterday










ContronThePanda is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















ContronThePanda is a new contributor. Be nice, and check out our Code of Conduct.













ContronThePanda is a new contributor. Be nice, and check out our Code of Conduct.












ContronThePanda is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498685%2fexecutable-file-named-test-is-in-path-but-wont-run%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Fluorita

Image
Fluorita Fluorita (blau) amb pirita (daurat). Fórmula química CaF 2 Epònim fluor Localitat tipus Jáchymov Classificació Categoria Halurs Nickel-Strunz 10a ed. 3.AB.25 Nickel-Strunz 9a ed. 3.AB.25 Nickel-Strunz 8a ed. III/A.08 Dana 9.2.1.1 Heys 8.4.7 Propietats Sistema cristal·lí Cúbic Hàbit cristal·lí Sol presentar cubs; menys freqüentment dodecaedres. De vegades hexaoctaedres i tetrahexaedres. Per la combinació d'aquestes formes, les arestes dels cubs són sovint modificades. De vegades els cristalls poden presentar diferències de creixement entre les cares. Sovint s'observen cristalls compostos per sobrecreixement. Pot ser massiva, compacta, terrosa, columnar (poc freqüent), globular en agregats o botroïdal. Estructura cristal·lina a = 5.4626Å Simetria Classe (H-M): m 3 m (4/ m 3 2/ m ) - Hexoctaèdric; Grup espacial: Fm 3 m Color Blanc, groc, verd, violeta, vermell, rosa, blau o negre Mac...
Read more

Hulsita

Image
Hulsita Hulsita de la localitat tipus Fórmula química Fe 2+ 2 Fe 3+ O 2 BO 3 Epònim Alfred Hulse Brooks Localitat tipus mont Brooks, península de Seward, Nome Borough, Alaska, Estats Units Classificació Categoria borats Nickel-Strunz 10a ed. 6.AB.45 Nickel-Strunz 9a ed. 6.AB.45 Nickel-Strunz 8a ed. V/G.03 Dana 24.2.3.1 Heys 9.6.4 Propietats Sistema cristal·lí monoclínic Estructura cristal·lina a = 10,68Å; b = 3,09Å; c = 5,43Å; β = 94,15° Color negre Macles en [001]; un membre de la macla es troba girat 120° en relació a l'altre Exfoliació bona en {110} Duresa 3 Lluïssor vítria, submetàl·lica Densitat 4,28 g/cm 3 (mesurada); Més informació Estatus IMA mineral heretat (G) i mineral heretat (G) Any d'aprovació 1908 Referències [1] La hulsita és un mineral de la classe dels borats, que pertany al grup de la pinakiolita. Rep el seu nom en honor del nord-americà ...
Read more

Península de Txukotka

Image
Península de Txukotka Tipus Península Ubicació 66° N, 172° O  /  66°N , 172°O  / 66; -172 Mar mar dels Txuktxis La península de Txukotka a l'extrem oriental de Sibèria La península de Txukotka o península dels Txuktxis (en rus Чуко́тский полуо́стров , Txukotski poluóstrov ) és una península que es troba a l'extrem oriental d'Euràsia. Contingut 1 Descripció 2 Població 3 Vegeu també 4 Bibliografia Descripció L'estret de Bering, entre la península de Txukotka i la península de Seward a Alaska Foto de satèl·lit de la zona amb la península de Txukotka a l'esquerra El seu punt més extrem és el cap Dezhnev a la vora del nucli d'Uelen, un dels poquíssims llocs habitats de la zona. Al nord limita amb el mar dels Txuktxis i amb el mar de Bering al sud i amb l'estret de Bering a l'est. A la costa sud es troben la badia de Sant Lawrence i la badia de Kresta. La penínsu...
Read more