diff options
| author | Ralf Baechle <ralf@linux-mips.org> | 1998-05-07 02:55:41 +0000 |
|---|---|---|
| committer | Ralf Baechle <ralf@linux-mips.org> | 1998-05-07 02:55:41 +0000 |
| commit | dcec8a13bf565e47942a1751a9cec21bec5648fe (patch) | |
| tree | 548b69625b18cc2e88c3e68d0923be546c9ebb03 /Documentation/mandatory.txt | |
| parent | 2e0f55e79c49509b7ff70ff1a10e1e9e90a3dfd4 (diff) | |
o Merge with Linux 2.1.99.
o Fix ancient bug in the ELF loader making ldd crash.
o Fix ancient bug in the keyboard code for SGI, SNI and Jazz.
Diffstat (limited to 'Documentation/mandatory.txt')
| -rw-r--r-- | Documentation/mandatory.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/mandatory.txt b/Documentation/mandatory.txt index 1ef2788d8..bc449d49e 100644 --- a/Documentation/mandatory.txt +++ b/Documentation/mandatory.txt @@ -19,7 +19,7 @@ troublesome) is access to a user's mailbox. The mail user agent and the mail transfer agent must guard against updating the mailbox at the same time, and prevent reading the mailbox while it is being updated. -In a perfect world all process would use and honour a cooperative, or +In a perfect world all processes would use and honour a cooperative, or "advisory" locking scheme. However, the world isn't perfect, and there's a lot of poorly written code out there. @@ -47,8 +47,8 @@ scheme is defined by the System V Interface Definition (SVID) Version 3. 2. Marking a file for mandatory locking --------------------------------------- -A file is marked as a candidate for mandatory by setting the group-id bit in -its file mode but removing the group-execute bit. This is an otherwise +A file is marked as a candidate for mandatory locking by setting the group-id +bit in its file mode but removing the group-execute bit. This is an otherwise meaningless combination, and was chosen by the System V implementors so as not to break existing user programs. @@ -103,7 +103,7 @@ agree. 2. If a process has locked a region of a file with a mandatory read lock, then other processes are permitted to read from that region. If any of these processes attempts to write to the region it will block until the lock is - released, unless the process has opened the file opened with the O_NONBLOCK + released, unless the process has opened the file with the O_NONBLOCK flag in which case the system call will return immediately with the error status EAGAIN. @@ -145,7 +145,7 @@ better still fix the system calls yourself and submit a patch to me or Linus. 6. Warning! ----------- -Not even root can override a mandatory lock, so runaway process can wreak +Not even root can override a mandatory lock, so runaway processes can wreak havoc if they lock crucial files. The way around it is to change the file permissions (remove the setgid bit) before trying to read or write to it. Of course, that might be a bit tricky if the system is hung :-( |