i have a closed source program that prints output to standard output. i need to parse the output. so i redirect the output to a fifo (from which i can read in the parent process that forks and execs the binary) using dup2 and then exec the program. the problem is that the fprintf calls in the file become buffered because it is now writing to a file.
i tried calling setvbuf with _IONBF on stdout before calling exec. but the problem still exists.
why does setvbuf not help in my case?
how can i force the output to get flushed?
setvbuf()makes no difference because it changes the state of part of the C runtime library, not part of the OS. When the new process begins running, its C runtime library will be reinitialised (that’s if it uses a CRT at all!)The only way I have heard of for getting around this is to somehow fake a terminal to the process. That’s because most CRT libraries will by default perform only line buffering if they believe they are attached to an interactive terminal (in the Unix world: if
isatty()returns true on the file descriptor), whereas otherwise they will buffer in larger blocks (typically 8Kb or so).This utility looks like a pretty good place to start. (Borrowed from a comment on Trick an application into thinking its stdin is interactive, not a pipe, which has other useful info.)