Import named-lock am: 10099b967d am: a251f02d3c am: 2918246d30 am: 8c455a7a24 am: 37ff3bdb97 am: c443e836d5

Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/named-lock/+/2566511

Change-Id: Ib5a5f26f82295c6153d3048f8a341a48b698175c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: fe7bf0f76ec4187fddac28beafd69348da03ac13
  1. src/
  2. Cargo.toml
  3. Cargo.toml.orig
  4. CHANGELOG.md
  5. LICENSE
  6. METADATA
  7. MODULE_LICENSE_MIT
  8. OWNERS
  9. README.md
  10. rustfmt.toml
README.md

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.