14 releases
0.10.2 | Sep 1, 2024 |
---|---|
0.10.1 | Jul 19, 2023 |
0.9.1 | Jan 30, 2023 |
0.9.0 | Dec 28, 2022 |
0.3.0 |
|
#21 in Unix APIs
230,292 downloads per month
Used in 196 crates
(51 directly)
180KB
5K
SLoC
rlimit
Resource limits.
Documentation: https://docs.rs/rlimit
Contributing
Sponsor
If my open-source work has been helpful to you, please sponsor me.
Every little bit helps. Thank you!
lib.rs
:
rlimit - Resource limits.
Set resource limit
use rlimit::{setrlimit, Resource};
const DEFAULT_SOFT_LIMIT: u64 = 4 * 1024 * 1024;
const DEFAULT_HARD_LIMIT: u64 = 8 * 1024 * 1024;
assert!(Resource::FSIZE.set(DEFAULT_SOFT_LIMIT, DEFAULT_HARD_LIMIT).is_ok());
let soft = 16384;
let hard = soft * 2;
assert!(setrlimit(Resource::NOFILE, soft, hard).is_ok());
Get resource limit
use rlimit::{getrlimit, Resource};
assert!(Resource::NOFILE.get().is_ok());
assert_eq!(getrlimit(Resource::CPU).unwrap(), (rlimit::INFINITY, rlimit::INFINITY));
Windows
Windows does not have Unix-like resource limits. It only supports changing the number of simultaneously open files currently permitted at the stdio level.
See the official documentation of
_getmaxstdio
and
_setmaxstdio
.
println!("{}", rlimit::getmaxstdio()); // 512
rlimit::setmaxstdio(2048).unwrap();
println!("{}", rlimit::getmaxstdio()); // 2048
Increase NOFILE limit
See the example nofile.
You can also use the tool function rlimit::increase_nofile_limit
rlimit::increase_nofile_limit(10240).unwrap();
rlimit::increase_nofile_limit(u64::MAX).unwrap();
Troubleshoot
Failed to increase NOFILE to hard limit on macOS
On macOS, getrlimit by default reports that the hard limit is
unlimited, but there is usually a stricter hard limit discoverable
via sysctl (kern.maxfilesperproc
). Failing to discover this secret stricter hard limit will
cause the call to setrlimit to fail.
rlimit::increase_nofile_limit
respects kern.maxfilesperproc
.