Bash not recognising built-in shell commands

waffle0007 · 2024-02-25 23:09:26

When running a script containing

#!/usr/bin/env bash
which foo

$ ./test.sh
./test.sh: line 2: which: command not found

The same happens with various interpreter variations

#!/bin/bash
#!/usr/bin/bash
#!/bin/sh
# etc.

However, 'zsh' does work, for what it's worth. Please let me know if I can provide any additional information.

V1del · 2024-02-25 23:41:36

which is a program and a package not a built-in. Is your PATH broken? Are you using lightdm? It recently had an adjustment of it's session handling when using different shells and that caused some issues. echo your $PATH in one of the failing scripts.

WorMzy · 2024-02-25 23:42:30

What makes you think that 'which' is a bash builtin?

bash$ type which
which is /usr/bin/which

If your script doesn't set PATH, call the binary by it's absolute path.

seth · 2024-02-26 08:57:12

Friendly reminder to better not engage in whichcraft at all

Arch Linux

#1 2024-02-25 23:09:26

Bash not recognising built-in shell commands

#2 2024-02-25 23:41:36

Re: Bash not recognising built-in shell commands

#3 2024-02-25 23:42:30

Re: Bash not recognising built-in shell commands

#4 2024-02-26 08:57:12

Re: Bash not recognising built-in shell commands

Board footer