Linux backend

Open
  • Is something wrong?
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, rust
Domain
backend, operating-systems

Research direction

Start by reading the per-operating-system seam and the existing Windows backend, then check how the project launches and supervises child processes. Implement the Linux cgroup v2 backend with the stated refusal behavior when no writable delegated cgroup is available. Verify that it ends the process tree at the deadline and respects the documented limits and kernel requirements.

Written by the indexing model from the issue text.

Description

platform roadmap

A Linux backend built on cgroup v2: a delegated cgroup per run, the child placed in it before exec, cgroup.kill at the deadline, the guard as subreaper, owners watched by pidfd, and a watchdog for the guard's own end. With no writable delegated cgroup the guard refuses (exit 125); there is no weaker mode.

Declared limits: a process started through the user service manager is not reached; the tree survives if the guard and its watchdog are both killed.

Minimum kernel: 5.14 (cgroup.kill), 5.3 (pidfd_open). Depends on the per operating system seam.

Dominant language
Rust
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WikdSolvemProbler/process-tree-guard

All issues in WikdSolvemProbler/process-tree-guard

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.