tmp/tmpifxw_cx5/{from.md → to.md}
RENAMED
|
@@ -1,13 +1,16 @@
|
|
| 1 |
#### File system race behavior <a id="fs.race.behavior">[[fs.race.behavior]]</a>
|
| 2 |
|
| 3 |
-
|
| 4 |
-
|
|
|
|
|
|
|
|
|
|
| 5 |
|
| 6 |
If the possibility of a file system race would make it unreliable for a
|
| 7 |
program to test for a precondition before calling a function described
|
| 8 |
-
herein, *
|
| 9 |
|
| 10 |
[*Note 1*: As a design practice, preconditions are not specified when
|
| 11 |
it is unreasonable for a program to detect them prior to calling the
|
| 12 |
function. — *end note*]
|
| 13 |
|
|
|
|
| 1 |
#### File system race behavior <a id="fs.race.behavior">[[fs.race.behavior]]</a>
|
| 2 |
|
| 3 |
+
A *file system race* is the condition that occurs when multiple threads,
|
| 4 |
+
processes, or computers interleave access and modification of the same
|
| 5 |
+
object within a file system. Behavior is undefined if calls to functions
|
| 6 |
+
provided by subclause [[fs.race.behavior]] introduce a file system
|
| 7 |
+
race.
|
| 8 |
|
| 9 |
If the possibility of a file system race would make it unreliable for a
|
| 10 |
program to test for a precondition before calling a function described
|
| 11 |
+
herein, *Preconditions:* is not specified for the function.
|
| 12 |
|
| 13 |
[*Note 1*: As a design practice, preconditions are not specified when
|
| 14 |
it is unreasonable for a program to detect them prior to calling the
|
| 15 |
function. — *end note*]
|
| 16 |
|