| commit | 3175384477054166113dd3bbd0a0ce7705fe62de | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Fri Sep 29 01:13:03 2023 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Fri Sep 29 01:13:03 2023 +0000 |
| tree | d8346e1ebbd2f24b962d129ad99a003ad6f27157 | |
| parent | 61136a56c71bbf47327636b6abd9e276db2a25f9 [diff] | |
| parent | 674e12f438e47810e87d5e7fa96c9b73c29fe86d [diff] |
Snap for 10878163 from 674e12f438e47810e87d5e7fa96c9b73c29fe86d to 24D1-release Change-Id: I887a6cf843ab1a9e5e2678281254945c584b89af
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.