fcntl.2: Minor change: move some NOTES text on record locking

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/fcntl.2 b/man2/fcntl.2
index bf792d1bfd119cf5d667c2499ebcaa2dfadddd16..3253e09befa28d6eb9c1709fe9158a772460e65d 100644 (file)
--- a/man2/fcntl.2
+++ b/man2/fcntl.2
@@ -1274,6 +1274,27 @@ Clearly,
 .I l_pid
 alone is not going to be very useful if the process holding the lock
 may live on a different machine.
+
+The original Linux
+.BR fcntl ()
+system call was not designed to handle large file offsets
+(in the
+.I flock
+structure).
+Consequently, an
+.BR fcntl64 ()
+system call was added in Linux 2.4.
+The newer system call employs a different structure for file locking,
+.IR flock64 ,
+and corresponding commands,
+.BR F_GETLK64 ,
+.BR F_SETLK64 ,
+and
+.BR F_SETLKW64 .
+However, these details can be ignored by applications using glibc, whose
+.BR fcntl ()
+wrapper function transparently employs the more recent system call
+where it is available.
 .SS Record locking and NFS
 Before Linux 3.12, if an NFSv4 client
 loses contact with the server for a period of time