我在bash中使用花括号在表达式中添加了两次美元符号:

cp -r $PROJECT_NAME ${$PROJECT_NAME}2

而不是

cp -r $PROJECT_NAME ${PROJECT_NAME}2

在我的例子中(在ubuntu 18.04下)，我混合了$(${})，工作正常:

BACKUPED_NB=$(ls ${HOST_BACKUP_DIR}*${CONTAINER_NAME}.backup.sql.gz | wc --lines)

完整的例子。

Ubuntu下的默认shell (/bin/sh)指向dash，而不是bash。

me@pc:~$ readlink -f $(which sh)
/bin/dash

所以如果你chmod +x your_script_file.sh，然后用。/your_script_file.sh运行它，或者如果你用bash your_script_file.sh运行它，它应该工作得很好。

使用sh your_script_file.sh运行它将不起作用，因为散列行将被忽略，脚本将由dash解释，dash不支持字符串替换语法。

看起来“+x”会导致问题:

root@raspi1:~# cat > /tmp/btest
#!/bin/bash

jobname="job_201312161447_0003"
jobname_pre=${jobname:0:16}
jobname_post=${jobname:17}
root@raspi1:~# chmod +x /tmp/btest
root@raspi1:~# /tmp/btest
root@raspi1:~# sh -x /tmp/btest
+ jobname=job_201312161447_0003
/tmp/btest: 4: /tmp/btest: Bad substitution

您的脚本语法是有效的bash和良好的。

故障可能原因:

Your bash is not really bash but ksh or some other shell which doesn't understand bash's parameter substitution. Because your script looks fine and works with bash. Do ls -l /bin/bash and check it's really bash and not sym-linked to some other shell. If you do have bash on your system, then you may be executing your script the wrong way like: ksh script.sh or sh script.sh (and your default shell is not bash). Since you have proper shebang, if you have bash ./script.sh or bash ./script.sh should be fine.

尝试使用bash命令显式地运行脚本，而不是将其作为可执行文件执行。