fslock-guard
| Crates.io | fslock-guard |
| lib.rs | fslock-guard |
| version | |
| source | src |
| created_at | 2024-02-05 18:40:35.438691 |
| updated_at | 2025-01-07 17:17:59.903266 |
| description | Wrapper around a lockfile with unlock-on-drop semantics |
| homepage | https://gitlab.torproject.org/tpo/core/arti/-/wikis/home |
| repository | https://gitlab.torproject.org/tpo/core/arti.git/ |
| max_upload_size | |
| id | 1127843 |
| Cargo.toml error: | TOML parse error at line 22, column 1 | 22 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
David Goulet (dgoulet-tor)
documentation
README
fslock-guard — A guard object to ensure we have an exclusive lock to a file
This crate is a thin wrapper around fslock, which uses flock(2) or
LockFileEx to acquire an advisory lock on the filesystem.
We add two features that fslock does not (currently) have:
- We have a [
LockFileGuard] type, which can be used to ensure that a lock is actually held until the guard is dropped. - We perform a post-lock check to make sure that our lockfile has not been removed and re-created on disk by someone else. This check makes it safe to remove lockfiles.