You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, when you import the procd like this, the script shows an error when it calls 'basename' trying to obtain the procd lock.
cat /tmp/test.sh
#!/bin/sh
set -x
. /lib/functions/procd.sh
/tmp/test.sh 2>&1|grep basename -C2
readlink
local 'basescript='
basename
BusyBox v1.30.1 () multi-call binary.
Usage: basename FILE [SUFFIX]
Strip directory path and .SUFFIX from FILE
`
Either procd.sh should be updated so that it can be called outside of init scripts without printing warnings, or the documentation should be updated to reflect that procd should not be called outside init scripts.
The text was updated successfully, but these errors were encountered:
aaronjg:
The documentation here: https://openwrt.org/docs/guide-developer/procd-init-scripts suggests that you can use procd outside of init scripts.:
However, when you import the procd like this, the script shows an error when it calls 'basename' trying to obtain the procd lock.
cat /tmp/test.sh
#!/bin/sh
set -x
. /lib/functions/procd.sh
/tmp/test.sh 2>&1|grep basename -C2
BusyBox v1.30.1 () multi-call binary.
Usage: basename FILE [SUFFIX]
Strip directory path and .SUFFIX from FILE
`
Either procd.sh should be updated so that it can be called outside of init scripts without printing warnings, or the documentation should be updated to reflect that procd should not be called outside init scripts.
The text was updated successfully, but these errors were encountered: