diff options
| author | Lennart Poettering <lennart@poettering.net> | 2018-11-29 11:17:36 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2018-11-29 15:29:47 +0100 |
| commit | edc8e7b81f061dec9871f8255741f1f8964d82b6 (patch) | |
| tree | 6cc2c80f911630b005300dba5a340b35d3f73f0f /docs/BLOCK_DEVICE_LOCKING.md | |
| parent | c1d3483d475fc226f50ce499dc7894ddd3274d87 (diff) | |
| download | systemd-edc8e7b81f061dec9871f8255741f1f8964d82b6.tar.gz | |
docs: fix typo
Diffstat (limited to 'docs/BLOCK_DEVICE_LOCKING.md')
| -rw-r--r-- | docs/BLOCK_DEVICE_LOCKING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/BLOCK_DEVICE_LOCKING.md b/docs/BLOCK_DEVICE_LOCKING.md index bf84484255..ceb060c0c9 100644 --- a/docs/BLOCK_DEVICE_LOCKING.md +++ b/docs/BLOCK_DEVICE_LOCKING.md @@ -55,7 +55,7 @@ take a `LOCK_EX` *exclusive* lock instead. For further details, see the And please keep in mind: BSD file locks (`flock()`) and POSIX file locks (`lockf()`, `F_SETLK`, …) are different concepts, and in their effect orthogonal. The scheme discussed above uses the former and not the latter, -because the these types of locks more closely match the required semantics. +because these types of locks more closely match the required semantics. Summarizing: it is recommended to take `LOCK_EX` BSD file locks when manipulating block devices in all tools that change file system block devices |