Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#3291 - procd gives warning when called outside an init script #6425

Open
openwrt-bot opened this issue Aug 18, 2020 · 0 comments
Open

FS#3291 - procd gives warning when called outside an init script #6425

openwrt-bot opened this issue Aug 18, 2020 · 0 comments
Labels

Comments

@openwrt-bot
Copy link

aaronjg:

The documentation here: https://openwrt.org/docs/guide-developer/procd-init-scripts suggests that you can use procd outside of init scripts.:

Note You can also send signals to named procd services from outside initscripts. Simply load the procd functions and send the signal as before.

#!/bin/sh
. /lib/functions/procd.sh
procd_send_signal service_name [instance_name] [signal]

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant