commit | 840aa2b5ececb9c07596b427a3341108e6f84541 | [log] [tgz] |
---|---|---|
author | Andrew Walbran <qwandor@google.com> | Mon Nov 20 19:44:56 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Nov 20 19:44:56 2023 +0000 |
tree | 7b96be3a97e36557820b6838dcd0ab5c52375c5e | |
parent | 3e2d24188dd9ff0470b5be1329d39a2ecf407bb1 [diff] | |
parent | aec58de3216e67cf2b08eb657f4674c859e6f497 [diff] |
Migrate to cargo_embargo. am: c7430c0513 am: aec58de321 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/named-lock/+/2837827 Change-Id: Ib31c90346cb968f1a38616a9e4401fedd0e28e29 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
.