#cross-process #api #locking

proc-lock

A simple cross-process locking API

5 releases

0.4.0 Mar 23, 2022
0.3.3 Mar 22, 2022
0.3.2 Mar 17, 2022
0.3.1 Mar 17, 2022
0.3.0 Mar 17, 2022

#1665 in Concurrency

Download history 1110/week @ 2025-10-14 1090/week @ 2025-10-21 850/week @ 2025-10-28 1128/week @ 2025-11-04 775/week @ 2025-11-11 1309/week @ 2025-11-18 983/week @ 2025-11-25 1072/week @ 2025-12-02 690/week @ 2025-12-09 948/week @ 2025-12-16 442/week @ 2025-12-23 720/week @ 2025-12-30 686/week @ 2026-01-06 793/week @ 2026-01-13 1119/week @ 2026-01-20 1458/week @ 2026-01-27

4,219 downloads per month
Used in 4 crates (3 directly)

MIT license

7KB
78 lines

Developed with ❤️ by Tabnine

Proc-lock

A simple cross-process locking API.

Quick Start

Installation

In your Cargo.toml file, add:

[dependencies]
proc-lock = "*"

Using the API directly

use proc_lock::{lock, LockPath};

fn main() {
    let lock_path = LockPath::Tmp("my_lock.lock");
    let guard = lock(&lock_path).unwrap();
    // Until `guard` is dropped, this code section is atomic across multiple processes.
    // ...
    drop(guard);
}

Using macros

use proc_lock::proclock;

fn main() {
 // A lock will be acquired at the beginning of this function, and will be released at the end.
 a_sensitive_function();
}

#[proc_lock(name = "my_lock.lock")]
fn a_sensitive_function() {}

Current status

⚠️This crate is in its early stages, breaking changes are expected in upcoming releases.

Changelog

  • 0.4.0 - Change interdependencies to local for better development process
  • 0.3.3 - Minor docs changes
  • 0.3.2 - Fix macro compilation
  • 0.3.1 - Change docs
  • 0.3.0 - [breaking changes] Rename crate to proc-lock, and the macro to proc_lock
  • 0.2.1 - Add a notice about renaming the crate
  • 0.2.0 - [breaking changes] Stop supporting non-blocking macro api

Contribution

Please refer to our project, as well as open issues.

Also feel free to discuss and open PRs regardless :)

Dependencies

~2.5MB
~49K SLoC