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