netifd: protocol script can't normally start more than one demon process
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Description
I was writing protocol script for netifd and had a trouble managing two daemon processes for the same interface.
When multiple proc_run_command functions are invoked, each one terminates previously spawned process and starts new one.
Example
Use case can be found there along with a nasty workaround.
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 locating the proc_run_command implementation and reading how repeated invocations track and terminate daemon processes. Compare that behavior with the yggdrasil.sh example linked in the issue. Done means a protocol script can manage multiple daemon processes for one interface without a later invocation terminating an earlier process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100