Grabbing output from exec

Question

I'm trying to write a C program that grabs command output and then i'll be passing that to another program.

I'm having an issue, I cant work out how to get the command output and store it. Below is a sample of what I have

if(fork() == 0){ execl("/bin/ls", "ls", "-1", (char *)0); /* do something with the output here */ } else{ //*other stuff goes here* }

so basically im wondering if there is any way i can get the output from the "execl" and pass it to some thing else (e.g. via storing it in some kind of buffer).

Suggestions would be great.

Jonathan Leffler · Accepted Answer · 2014-11-26 05:32:22Z

You have to create a pipe from the parent process to the child, using pipe(). Then you must redirect standard ouput (STDOUT_FILENO) and error output (STDERR_FILENO) using dup or dup2 to the pipe, and in the parent process, read from the pipe. It should work.

#include <stdio.h> #include <stdlib.h> #include <unistd.h> #define die(e) do { fprintf(stderr, "%s\n", e); exit(EXIT_FAILURE); } while (0); int main() { int link[2]; pid_t pid; char foo[4096]; if (pipe(link)==-1) die("pipe"); if ((pid = fork()) == -1) die("fork"); if(pid == 0) { dup2 (link[1], STDOUT_FILENO); close(link[0]); close(link[1]); execl("/bin/ls", "ls", "-1", (char *)0); die("execl"); } else { close(link[1]); int nbytes = read(link[0], foo, sizeof(foo)); printf("Output: (%.*s)\n", nbytes, foo); wait(NULL); } return 0; }

I can read the man pages on dup2, execl, etc, which explains the function calls, but I don't understand the overall picture. Can somebody elaborate why we need to fork? Why do we close the links when we do, and why the wait(NULL) at the end?
Indeed fork might not be needed. But if you want to perform operations at the end of the chile task, you have to fork a new process. Wait ensures that parent's process don't quit bedore child.
I found this explanation in my copy of APUE, section 1.6: "In the child, we call exec to execute the command [...]. This replaces the child process with the new program file. The combination of fork followed by exec is called spawning a new process on some operating systems. In the UNIX System, the two parts are separated into individual functions."
Okay, all starting to make sense now. From the man page: "The exec() family of functions replaces the current process image with a new process image."

ceph3us · Accepted Answer · 2021-03-02 15:43:58Z

Open a pipe, and change stdout to match that pipe.

 #include <sys/types.h> #include <unistd.h> #include <stdio.h> #include <stdlib.h> int pipes[2]; pipe(pipes); // Create the pipes dup2(pipes[1],1); // Set the pipe up to standard output

After that, anything which goes to stdout,(such as through printf), comes out pipe[0].

FILE *input = fdopen(pipes[0],"r");

Now you can read the output like a normal file descriptor. For more details, look at this

user2420449 · Accepted Answer · 2017-05-31 09:35:04Z

Thanks Jonathan Leffler, and i optimize the above code for it can't read all response for one time.

#include <stdio.h> #include <stdlib.h> #include <unistd.h> #include <string.h> #include <sys/wait.h> #define die(e) do { fprintf(stderr, "%s\n", e); exit(EXIT_FAILURE); } while (0); int main() { int link[2]; pid_t pid; char foo[4096 + 1]; memset(foo, 0, 4096); if (pipe(link)==-1) die("pipe"); if ((pid = fork()) == -1) die("fork"); if(pid == 0) { dup2 (link[1], STDOUT_FILENO); close(link[0]); close(link[1]); execl("/bin/ls", "ls", "-1", (char *)0); die("execl"); } else { close(link[1]); int nbytes = 0; std::string totalStr; while(0 != (nbytes = read(link[0], foo, sizeof(foo)))) { totalStr = totalStr + foo; printf("Output: (%.*s)\n", nbytes, foo); memset(foo, 0, 4096); } wait(NULL); } return 0; }

ericcurtin · Accepted Answer · 2021-05-19 16:11:26Z

If you want the output in a string (char *), here's an option (for Linux at least):

#include <errno.h> #include <stdio.h> #include <stdlib.h> #include <sys/uio.h> #include <sys/wait.h> #include <unistd.h> char* qx(char** cmd, int inc_stderr) { int stdout_fds[2]; pipe(stdout_fds); int stderr_fds[2]; if (!inc_stderr) { pipe(stderr_fds); } const pid_t pid = fork(); if (!pid) { close(stdout_fds[0]); dup2(stdout_fds[1], 1); if (inc_stderr) { dup2(stdout_fds[1], 2); } close(stdout_fds[1]); if (!inc_stderr) { close(stderr_fds[0]); dup2(stderr_fds[1], 2); close(stderr_fds[1]); } execvp(*cmd, cmd); exit(0); } close(stdout_fds[1]); const int buf_size = 4096; char* out = malloc(buf_size); int out_size = buf_size; int i = 0; do { const ssize_t r = read(stdout_fds[0], &out[i], buf_size); if (r > 0) { i += r; } if (out_size - i <= 4096) { out_size *= 2; out = realloc(out, out_size); } } while (errno == EAGAIN || errno == EINTR); close(stdout_fds[0]); if (!inc_stderr) { close(stderr_fds[1]); do { const ssize_t r = read(stderr_fds[0], &out[i], buf_size); if (r > 0) { i += r; } if (out_size - i <= 4096) { out_size *= 2; out = realloc(out, out_size); } } while (errno == EAGAIN || errno == EINTR); close(stderr_fds[0]); } int r, status; do { r = waitpid(pid, &status, 0); } while (r == -1 && errno == EINTR); out[i] = 0; return out; } int main() { char* argv[3]; argv[0] = "ls"; argv[1] = "-la"; argv[2] = NULL; char* out = qx(argv, 0); printf("%s", out); free(out); }

michele sponchiado · Accepted Answer · 2024-06-17 12:34:29Z

The reply here is what I use in my code, and it works fine, but I think it needs a little improvement: we need to move the read AFTER the wait, else there could be a race between the child and the original processes and the read result may be unpredictable, i.e. you could read a previous reply, or just a part of the expected current reply.

I post the same code as here, just adjusting the wait() position and adding some comments:

#include <stdio.h> #include <stdlib.h> #include <unistd.h> #define die(e) do { fprintf(stderr, "%s\n", e); exit(EXIT_FAILURE); } while (0); int main() { int link[2]; pid_t pid; char foo[4096]; if (pipe(link)==-1) die("pipe"); if ((pid = fork()) == -1) die("fork"); if(pid == 0) { dup2 (link[1], STDOUT_FILENO); close(link[0]); close(link[1]); execl("/bin/ls", "ls", "-1", (char *)0); die("execl"); } else { close(link[1]); wait(NULL); // N.B.: wait until the child process completes, else we could read a partial or empty output const int nbytes = read(link[0], foo, sizeof(foo)); // read the output once the child has completed printf("Output: (%.*s)\n", nbytes, foo); } return 0; }

There's no answer by Jonathan (and if there were, you wouldn't know whether it's "above" or "below" for any given reader).
This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review
Thanks, Mr Charrière for your reply; unfortunately, my reputation is still too low to comment under the main answer, so I had to write a full reply hoping to be useful: I lost a couple of hours debugging the incomplete reply I was receiving from the child due to the wait race condition, and I was hoping to give a useful contribution...

Collectives™ on Stack Overflow

Grabbing output from exec

5 Answers 5

4 Comments

Comments

Comments

Comments

4 Comments

Hot Network Questions