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#2261 - commit baaf38c5e540b23ba086d94743de860b60c37161 prevents apps from storing runtime info in PROCD #7143

Open
openwrt-bot opened this issue Apr 28, 2019 · 1 comment
Labels

Comments

@openwrt-bot
Copy link

stangri:

This commit: https://git.openwrt.org/?p=project/procd.git;a=commit;h=baaf38c5e540b23ba086d94743de860b60c37161 deletes the PROCD instance on exit, however it is being used in the simple-adblock package https://github.com/openwrt/packages/blob/master/net/simple-adblock/files/simple-adblock.init#L141-L154 to store runtime info.

On snapshots this information now gets deleted.

Could the powers that be either:

  1. Offer an option to not automatically delete PROCD info on instance exit
  2. Rule that a misuse of PROCD so that I can then store runtime info on tmpfs instead

Don't know how to tag Kristian Evensen kristian.evensen@gmail.com and Hans Dedecker dedeckeh@gmail.com in the bug.

@openwrt-bot
Copy link
Author

jow-:

You can use the data object outside of the instance, e.g. ubus call service set '{ "name": "foo", "data": { "whatever": true } }' instead of { "name": "foo", "instances": [ {..., "data": { "whatever": true } } ] }.

If you cannot do this due to other constraints, then the only solution I see is setting an infinite sleep command instead of an empty command spec (or something with a very long sleep time, procd will relaunch it anyway).

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