commit | 3371b43948748142c8db70bf9abd52f26bb75def | [log] [tgz] |
---|---|---|
author | Elie Kheirallah <khei@google.com> | Fri Apr 28 18:47:22 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Apr 28 18:47:22 2023 +0000 |
tree | 54308d5981cefaec9928acbd579206e60d0fd8cd | |
parent | a251f02d3c9f09d0b88b4408a5b06d9ca82e771e [diff] | |
parent | 6ebd4d16ce86e64052dd4f5466ecca4bf798e18e [diff] |
Add Android.bp to named-lock am: 6ebd4d16ce Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/named-lock/+/2566512 Change-Id: I5fa02601cb0ee89e3eb2629de1a47d79629cdd11 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This crate provides a simple and cross-platform implementation of named locks. You can use this to lock sections between processes.
use named_lock::NamedLock; use named_lock::Result; fn main() -> Result<()> { let lock = NamedLock::create("foobar")?; let _guard = lock.lock()?; // Do something... Ok(()) }
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
.