-
Notifications
You must be signed in to change notification settings - Fork 93
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
wasm: add kuasar-wasm systemd service #86
Conversation
Please rebase your commits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
wasm/service/kuasar-wasm.service
Outdated
[Service] | ||
Type=simple | ||
ExecStart=/usr/local/bin/wasm-sandboxer --listen /run/wasm-sandboxer.sock --dir /run/kuasar-wasm | ||
ExecReload=/bin/kill -s HUP $MAINPID |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently wasm type sandboxer doesn't support config reload feature, ExecReload
needs to be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the consequence of keeping this ExecReload
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the user runs the systemctl reload wasm-sandboxer
command, the wasm-sandboxer process will receive the SIGHUP signal and process exit abnornally, which does not meet the expectation of the systemctl reload
command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
Signed-off-by: jwcesign <[email protected]>
wasm: add kuasar-wasm systemd service