Bug 24802
| Summary: | fcntl man page does not specify what happens to locks across exec | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | ingham <ingham> |
| Component: | Books & Articles | Assignee: | dd <dd> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->suspended Committed to -current, thanks! Will MFC after code freeze. Responsible Changed From-To: freebsd-doc->dd I'll mfc it. State Changed From-To: suspended->closed MFC'd. |
fcntl(2) does not mention what happens to locks when a process does an exec. Fix: Add the following paragraph: Locks obtained before an exec remain in effect until the new program releases them. If the new program does not know about the locks, they will not be released until the program exits. How-To-Repeat: read fcntl(2)