| Crates.io | cgroups-rs |
| lib.rs | cgroups-rs |
| version | 0.4.0 |
| created_at | 2020-12-21 08:27:35.886715+00 |
| updated_at | 2025-07-22 10:29:56.145351+00 |
| description | Native Rust crate for managing control groups on Linux |
| homepage | https://github.com/kata-containers/cgroups-rs |
| repository | https://github.com/kata-containers/cgroups-rs |
| max_upload_size | |
| id | 325143 |
| size | 480,109 |
Native Rust library for managing control groups under Linux
Both v1 and v2 of cgroups are supported.
use cgroups_rs::*;
use cgroups_rs::cgroup_builder::*;
// Acquire a handle for the cgroup hierarchy.
let hier = cgroups_rs::hierarchies::auto();
// Use the builder pattern (see the documentation to create the control group)
//
// This creates a control group named "example" in the V1 hierarchy.
let cg: Cgroup = CgroupBuilder::new("example")
.cpu()
.shares(85)
.done()
.build(hier);
// Now `cg` is a control group that gets 85% of the CPU time in relative to
// other control groups.
// Get a handle to the CPU controller.
let cpus: &cgroups_rs::cpu::CpuController = cg.controller_of().unwrap();
cpus.add_task(&CgroupPid::from(1234u64));
// [...]
// Finally, clean up and delete the control group.
cg.delete();
// Note that `Cgroup` does not implement `Drop` and therefore when the
// structure is dropped, the Cgroup will stay around. This is because, later
// you can then re-create the `Cgroup` using `load()`. We aren't too set on
// this behavior, so it might change in the feature. Rest assured, it will be a
// major version change.
This crate is licensed under:
at your option.
Please note that this crate is under heavy development, we will use sematic
versioning, but during the 0.0.* phase, no guarantees are made about
backwards compatibility.
Regardless, check back often and thanks for taking a look!