1 .\" Copyright (C) 2001 Andries Brouwer <aeb@cwi.nl>.
3 .\" %%%LICENSE_START(VERBATIM)
4 .\" Permission is granted to make and distribute verbatim copies of this
5 .\" manual provided the copyright notice and this permission notice are
6 .\" preserved on all copies.
8 .\" Permission is granted to copy and distribute modified versions of this
9 .\" manual under the conditions for verbatim copying, provided that the
10 .\" entire resulting derived work is distributed under the terms of a
11 .\" permission notice identical to this one.
13 .\" Since the Linux kernel and libraries are constantly changing, this
14 .\" manual page may be incorrect or out-of-date. The author(s) assume no
15 .\" responsibility for errors or omissions, or for damages resulting from
16 .\" the use of the information contained herein. The author(s) may not
17 .\" have taken the same level of care in the production of this manual,
18 .\" which is licensed free of charge, as they might when working
21 .\" Formatted or processed versions of this manual, if unaccompanied by
22 .\" the source, must acknowledge the copyright and authors of this work.
25 .TH FLOCKFILE 3 2021-03-22 "" "Linux Programmer's Manual"
27 flockfile, ftrylockfile, funlockfile \- lock FILE for stdio
32 .BI "void flockfile(FILE *" filehandle );
33 .BI "int ftrylockfile(FILE *" filehandle );
34 .BI "void funlockfile(FILE *" filehandle );
38 Feature Test Macro Requirements for glibc (see
39 .BR feature_test_macros (7)):
42 All functions shown above:
44 /* Since glibc 2.24: */ _POSIX_C_SOURCE >= 199309L
45 || /* Glibc <= 2.23: */ _POSIX_C_SOURCE
46 || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE
49 The stdio functions are thread-safe.
50 This is achieved by assigning
53 object a lockcount and (if the lockcount is nonzero)
55 For each library call, these functions wait until the
58 is no longer locked by a different thread, then lock it, do the
59 requested I/O, and unlock the object again.
61 (Note: this locking has nothing to do with the file locking done
67 All this is invisible to the C-programmer, but there may be two
68 reasons to wish for more detailed control.
69 On the one hand, maybe
70 a series of I/O actions by one thread belongs together, and should
71 not be interrupted by the I/O of some other thread.
72 On the other hand, maybe the locking overhead should be avoided
73 for greater efficiency.
75 To this end, a thread can explicitly lock the
78 then do its series of I/O actions, then unlock.
80 other threads from coming in between.
81 If the reason for doing
82 this was to achieve greater efficiency, one does the I/O with
83 the nonlocking versions of the stdio functions: with
97 no longer locked by a different thread, then makes the
98 current thread owner of
105 function decrements the lock count.
109 function is a nonblocking version
112 It does nothing in case some other thread
115 and it obtains ownership and increments
116 the lockcount otherwise.
120 function returns zero for success
121 (the lock was obtained), and nonzero for failure.
125 For an explanation of the terms used in this section, see
133 Interface Attribute Value
138 T} Thread safety MT-Safe
144 POSIX.1-2001, POSIX.1-2008.
146 These functions are available when
147 .B _POSIX_THREAD_SAFE_FUNCTIONS
150 .BR unlocked_stdio (3)