From db8caf03e5070781ee5109c88d8a79c1ba6e0c73 Mon Sep 17 00:00:00 2001
From: Ruslan Ermilov <ru@FreeBSD.org>
Date: Fri, 26 Oct 2001 17:38:20 +0000
Subject: Remove the internal implementation details of wrapping syscalls,
 which do not match the reality anyway.

Approved by:	deischen, bde
---
 lib/libc/sys/flock.2 | 21 ---------------------
 1 file changed, 21 deletions(-)

(limited to 'lib/libc/sys/flock.2')

diff --git a/lib/libc/sys/flock.2 b/lib/libc/sys/flock.2
index 33dcec5fff1e..f76b094450b8 100644
--- a/lib/libc/sys/flock.2
+++ b/lib/libc/sys/flock.2
@@ -112,27 +112,6 @@ forks and the child explicitly unlocks the file, the parent will
 lose its lock.
 .Pp
 Processes blocked awaiting a lock may be awakened by signals.
-.Sh IMPLEMENTATION NOTES
-In the non-threaded library
-.Fn flock
-is implemented as the
-.Va flock
-syscall.
-.Pp
-In the threaded library, the
-.Va flock
-syscall is assembled to
-.Fn _thread_sys_flock
-and
-.Fn flock
-is implemented as a function which locks
-.Fa fd
-for read and write, then calls
-.Fn _thread_sys_flock .
-Before returning,
-.Fn flock
-unlocks
-.Fa fd .
 .Sh RETURN VALUES
 .Rv -std flock
 .Sh ERRORS
-- 
cgit v1.3