read PIDs even if they arent in config.json
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- CSS
- Stars
- 1.1k
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
say you add a process with name 'foo' to config.json, start it, and then go to config.json and remove 'foo'.
now you are in a state where there is a foo.pid and foo.mon.pid, and the foo processes are likely running
IMO any PIDs that aren't referenced by 'config.json' should get SIGTERM'd and then deleted
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 by tracing how config.json entries are loaded and how the foo.pid and foo.mon.pid files are created or read. Check the process cleanup path and confirm how SIGTERM is handled. Done means PIDs no longer referenced by config.json are terminated and their PID files are deleted.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100