Limitcore Precheck
Open
Nobody has claimed this yet.
type/feature-request
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
Is your feature request related to a problem? Please describe:
Ref https://github.com/pingcap/tiup/pull/817
Describe the feature you'd like:
- Check if the deployment user can write to the core file directory permissions.
- e.g: redhat / centos
cat /proc/sys/kernel/core_pattern
- e.g: redhat / centos
- Example of adding a limit_core parameter to a document
- e.g:
limit_core: infinity
- e.g:
Why the featue is needed:
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
Contributor guide
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 reviewing the referenced pull request #817 and the deployment precheck flow, then inspect how Red Hat and CentOS expose /proc/sys/kernel/core_pattern. Done means checking whether the deployment user can write to the core file directory and supporting the documented limit_core: infinity configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100