What is wrong with fork processing file descriptors

This article mainly introduces "what is the situation of fork processing file descriptors". In the daily operation, I believe that many people have doubts about the situation of fork processing file descriptors. The editor consulted all kinds of data and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "what is the situation of fork processing file descriptors?" Next, please follow the editor to study!

There are two situations in which file descriptors are processed after fork:

1. The parent process waits for the child process to complete

The parent process does not need to do anything with its descriptor

Any shared descriptor that has been read / written by a child process after it terminates

The file offset has been updated accordingly

two。 The parent / child processes each execute different program segments

After fork, the parent / child processes each turn off file descriptors that they do not need to use

(commonly used in network service processes)

At this point, the study on "what happens to fork processing file descriptors" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!