refactor(cmd): use resty.signal for process signaling #11621
+727
−134
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Primary improvements:
os.execute()
for sending signalsSome months ago I needed to look over the code in
kong/cmd/utils/kill.lua
and thought to myself "we can do better than os.execute() here." At long last, here are the improvements that stemmed from that thought.Along the way I renamed the file to
kong/cmd/utils/process.lua
and changed the name of theis_running()
function toexists()
for aesthetic reasons. This and the other API changes to the file make the PR somewhat large, but these changes were done in separate commits, so review commit-by-commit if you want to have an easier read-through of the changes.There was a flaky test in
spec/02-integration/01-helpers/03-http_mock_spec.lua
that was giving me trouble. It was actually related to this problem domain (waiting for a pidfile to exist and contain a PID), so I fixed it here as well.Re-do #11382 without squashing, merge after #11620