| commit | 7abde901493660e484533d9b49e20338bb3078b2 | [log] [tgz] |
|---|---|---|
| author | Andrew Walbran <[email protected]> | Mon Nov 20 20:18:07 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Mon Nov 20 20:18:07 2023 +0000 |
| tree | 7b96be3a97e36557820b6838dcd0ab5c52375c5e | |
| parent | 674e12f438e47810e87d5e7fa96c9b73c29fe86d [diff] | |
| parent | 840aa2b5ececb9c07596b427a3341108e6f84541 [diff] |
Migrate to cargo_embargo. am: c7430c0513 am: aec58de321 am: 840aa2b5ec Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/named-lock/+/2837827 Change-Id: Ie3e6455153a3b9e223441590b5fe794c7ea8207a 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.