管道:关闭管道数组中的文件描述符

问题描述 投票:0回答:1

我现在正在学习Linux并为我的系统编程课程提供管道,我现在很难理解在管道数组中关闭文件描述符。

 // write the code to loop over the command line arguments (remember to skip the executable name)
for (int i = 1; i < argc; i++) {
    // call pipe before we fork
    if ((pipe(pipe_fd[i-1])) == -1) {
        perror("pipe");
        exit(1);
    }
    // call fork
    int result = fork();
    if (result < 0) {   // case: a system call error
        // handle the error
        perror("fork");
        exit(1);
    } else if (result == 0) {  // case: a child process
        // child does their work here
        // child only writes to the pipe so close reading end
        if (close(pipe_fd[i-1][0]) == -1) {
            perror("close reading end from inside child");
            exit(1);
        }
        // before we forked the parent had open the reading ends to
        // all previously forked children -- so close those
        int child_no;
        for (child_no = 0; child_no < i-1; child_no++) {
            if (close(pipe_fd[child_no][0]) == -1) {
                perror("close reading ends of previously forked children");
                exit(1);
            }
        }
        int len = strlen(argv[i]);
        // write len to the pipe as an integer
        if (write(pipe_fd[i-1][1], &len, sizeof(int)) != sizeof(int)) {
            perror("write from child to pipe");
            exit(1);
        }
        // I'm done with the pipe so close it
        if (close(pipe_fd[i-1][1]) == -1) {
            perror("close pipe after writing");
            exit(1);
        }
        // exit so I don't fork my own children on next loop iteration
        exit(0);
    } else {
        // in the parent but before doing the next loop iteration
        // close the end of the pipe that I don't want open
        if (close(pipe_fd[i-1][1]) == -1) {
            perror("close writing end of pipe in parent");
            exit(1);
        }
    }
}

我将列出我现在理解的内容:

  1. 我理解父子进程需要关闭那些他们不需要使用的fds,在这种情况下,child正在写父进程,所以parent需要关闭写端口,而child需要关闭read port。
  2. 我理解文件描述符在父进程和子进程之间共享。

上面的代码是从我的演讲幻灯片中给出的,我特别感到困惑。

在循环中,我观察到一旦这个子被fork创建,每个子节点都在关闭它的读取端口,执行此操作的代码是:

else if (result == 0) {  // case: a child process
    // child does their work here
    // child only writes to the pipe so close reading end
    if (close(pipe_fd[i-1][0]) == -1) {
        perror("close reading end from inside child");
        exit(1);
    }

从我在这一点上的理解是,每个孩子在分娩后都要关闭自己的阅读口,我认为后者的孩子们不应该担心关闭以前孩子的阅读口岸。

但在阅读此代码后,我的理解似乎不正确:

        // before we forked the parent had open the reading ends to
    // all previously forked children -- so close those
    int child_no;
    for (child_no = 0; child_no < i-1; child_no++) {
        if (close(pipe_fd[child_no][0]) == -1) {
            perror("close reading ends of previously forked children");
            exit(1);
        }
    }

我不明白为什么后面的孩子应该关闭以前的孩子的阅读港口,这些孩子被创建后,这些阅读港口是不是已经关闭了?

谢谢你的协助。 :)

c linux pipe system-calls
1个回答
0
投票

描述符在它打开的所有进程关闭之前不会真正关闭。由于每个子进程都继承了前一进程中的所有管道描述符,因此它们应该关闭所有未使用的进程。

关闭读取端口的主要原因是,如果读取器退出后尝试写入管道,写入过程将收到错误或信号。如果其他孩子保持所有阅读端口都打开,那么在所有后续孩子退出之前不会发生这种情况。

© www.soinside.com 2019 - 2024. All rights reserved.