commit | c851eff42741e3256f9d451945fd6c0377cb3b10 | [log] [tgz] |
---|---|---|
author | Bob Badour <bbadour@google.com> | Thu May 04 21:26:20 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu May 04 21:26:20 2023 +0000 |
tree | 83dae2a80d085f22951e1f33744a6d79277c7e3d | |
parent | 3371b43948748142c8db70bf9abd52f26bb75def [diff] | |
parent | aaea0878178334718dc55fd3745c0f8a538a43af [diff] |
[LSC] Add LOCAL_LICENSE_KINDS to external/rust/crates/named-lock am: aaea087817 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/named-lock/+/2579045 Change-Id: I01b74a0bbedfbd95cca29f51f87e561442090550 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
.