mirror of https://github.com/mkerrisk/man-pages
prctl.2: Note semantics of IO_FLUSHER state with respect to fork(2) and execve(2)
Reported-by: Mike Christie <mchristi@redhat.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
22a2e0553b
commit
f3c29937e6
|
@ -1401,6 +1401,11 @@ and
|
|||
.IR arg5
|
||||
must be zero.
|
||||
.IP
|
||||
The IO_FLUSHER state is inherited by a child process created via
|
||||
.BR fork (2)
|
||||
and is preserved across
|
||||
.BR execve (2).
|
||||
.IP
|
||||
Examples of IO_FLUSHER applications are FUSE daemons, SCSI device
|
||||
emulation daemons, and daemons that perform error handling like multipath
|
||||
path recovery applications.
|
||||
|
|
Loading…
Reference in New Issue