On Fri, Jan 10, 2014 at 2:41 AM, Jason A. Donenfeld <[email protected]> wrote: > and does its thing per usual. At the end, however, it does not exit. > Instead of waitpid()ing on it in close filter, we SIGSTOP it, put the > fds back in place, etc. Then the next time that filter is called, we > SIGCONT it, it reads the first N lines as arguments again, and so > forth. I'm most tempted to go with this approach at the moment.
Problems abound. This has race condition issues, where the parent process will SIGSTOP the child before the child can write its output. This could be fixed with a more complicated signaling protocol, but that's more complex than I'd like it. Back to the drawing board. _______________________________________________ CGit mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/cgit
