Skip to main content
deleted 1 character in body
Source Link
chepner
  • 7.8k
  • 1
  • 29
  • 28

Your problem is that you are invoking sh and not bash for your script in the shebang line. The syntactical convention of <(command) is a bashism that does not exist when invoked via sh, which emulates the Bourne ShellPOSIX shell (if /bin/sh is a symlink to /bin/bash).

Your problem is that you are invoking sh and not bash for your script in the shebang line. The syntactical convention of <(command) is a bashism that does not exist when invoked via sh, which emulates the Bourne Shell (if /bin/sh is a symlink to /bin/bash).

Your problem is that you are invoking sh and not bash for your script in the shebang line. The syntactical convention of <(command) is a bashism that does not exist when invoked via sh, which emulates the POSIX shell (if /bin/sh is a symlink to /bin/bash).

added 78 characters in body
Source Link
DopeGhoti
  • 79.2k
  • 10
  • 107
  • 141

Your problem is that you are invoking sh and not bash for your script in the shebang line. The syntactical convention of <(command) is a bashism that does not exist inwhen invoked via sh, which emulates the Bourne Shell (if /bin/sh is a symlink to /bin/bash).

Your problem is that you are invoking sh and not bash for your script in the shebang line. The syntactical convention of <(command) is a bashism that does not exist in the Bourne Shell.

Your problem is that you are invoking sh and not bash for your script in the shebang line. The syntactical convention of <(command) is a bashism that does not exist when invoked via sh, which emulates the Bourne Shell (if /bin/sh is a symlink to /bin/bash).

Source Link
DopeGhoti
  • 79.2k
  • 10
  • 107
  • 141

Your problem is that you are invoking sh and not bash for your script in the shebang line. The syntactical convention of <(command) is a bashism that does not exist in the Bourne Shell.