satellite/entrypoint: Ignore unset variable errors while checking for VALID_EXECUTABLE
Otherwise core and ranged loop fail at startup with "/entrypoint: line 94: $1: unbound variable" Change-Id: I45a318038cd937c11f6a00d506c339ba69ea07bf
This commit is contained in:
parent
1525324384
commit
f819b6a210
@ -90,10 +90,10 @@ if [ "${STORJUP_ROLE:-""}" ]; then
|
||||
fi
|
||||
|
||||
# for backward compatibility reason, we use argument as command, only if it's an executable (and use it as satellite flags oterwise)
|
||||
set +e
|
||||
set +eo nounset
|
||||
which "$1" > /dev/null
|
||||
VALID_EXECUTABLE=$?
|
||||
set -e
|
||||
set -eo nounset
|
||||
|
||||
if [ $VALID_EXECUTABLE -eq 0 ]; then
|
||||
# this is a full command (what storj-up uses)
|
||||
|
Loading…
Reference in New Issue
Block a user