openresty / openresty/lua-nginx-module
ngx.pipe.spawn shell mode child process not killed after openresty exits
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- C
- Stars
- 11.8k
- Forks
- 2.1k
- Avg merge
- 6h 1m
- Merged PRs (30d)
- 6
Description
When using ngx.pipe.spawn in shell mode (args is a string), sh -c in invoked internally.
While OpenResty exists, SIGKILL is sent to sh process, but it's not able to propogate to child process.
The child process is then left alive.
POC:
init_work_by_lua_block {
require("ngx.pipe").spawn("/tmp/a.py")
}
$ cat /tmp/a.py:
#!/usr/bin/env python3
import time
time.sleep(23333)
Then signal stop the OpenResty/Nginx process.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ngx.pipe.spawn in shell mode and reproduce the behavior using init_work_by_lua_block and /tmp/a.py. Trace shutdown after the OpenResty/Nginx process stops; done means the spawned child process is no longer left alive after the parent exits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python, shell
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100