5 releases (3 breaking)

0.4.1 Feb 28, 2024
0.4.0 Feb 28, 2024
0.3.0 Sep 17, 2022
0.2.0 Apr 21, 2022
0.1.1 Feb 8, 2020

#74 in Operating systems

Download history 14235/week @ 2024-08-27 17277/week @ 2024-09-03 18388/week @ 2024-09-10 16512/week @ 2024-09-17 19697/week @ 2024-09-24 19631/week @ 2024-10-01 19608/week @ 2024-10-08 21179/week @ 2024-10-15 22104/week @ 2024-10-22 19640/week @ 2024-10-29 14035/week @ 2024-11-05 17914/week @ 2024-11-12 19368/week @ 2024-11-19 13613/week @ 2024-11-26 18045/week @ 2024-12-03 13638/week @ 2024-12-10

67,769 downloads per month
Used in 138 crates (6 directly)

MIT license

18KB
328 lines

named-lock

license crates.io docs

This crate provides a simple and cross-platform implementation of named locks. You can use this to lock sections between processes.

Example

use named_lock::NamedLock;
use named_lock::Result;

fn main() -> Result<()> {
    let lock = NamedLock::create("foobar")?;
    let _guard = lock.lock()?;

    // Do something...

    Ok(())
}

Implementation

On UNIX this is implemented by using files and flock. The path of the created lock file will be $TMPDIR/<name>.lock, or /tmp/<name>.lock if TMPDIR environment variable is not set.

On Windows this is implemented by creating named mutex with CreateMutexW.

Dependencies

~0.6–36MB
~552K SLoC