Steps to control an errant job
Open
Nobody has claimed this yet.
documentation
- Dominant language
- C
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 140
Description
I can't find out how you deal with a long running job. I can't work out how to skip it. Could this be please better documented? I've had a couple instances where my machine failed to boot or shutdown because of it.
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 locating the documentation for controlling or skipping long-running jobs during boot and shutdown. Document the supported way to handle an errant job, including recovery when it blocks boot or shutdown; done when users can find and follow those steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100