| commit | e0016be474abe88fdc0ed58cafc32a327ec7993c | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Wed May 22 23:09:25 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed May 22 23:09:25 2024 +0000 |
| tree | 57d115b505e55dc06848c14d020d46b6c3b00c3c | |
| parent | 5465fcf05c799f9b99e4f21e39669e572384306c [diff] | |
| parent | b32bd00e6b1c717bb3e9bc53ca32c6a5423d39f3 [diff] |
Update Android.bp by running cargo_embargo am: b32bd00e6b Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/named-lock/+/3096238 Change-Id: I4b313a19f1f41153e67f3bbcbaec4493296d2676 Signed-off-by: Automerger Merge Worker <[email protected]>
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.