Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    FWIW you have a fairly (well, slightly) strange setup here, using tail -f to provide continuous input to a program and tee to process the output. If you were still in need of an answer, I would have suggested simplifying the chain to <in.json jq '.f1' >out.json so that you could narrow down what's causing it. Commented Apr 4, 2018 at 7:23
  • See also BashFAQ #9 - What is buffering? Or, why does my command line produce no output: tail -f logfile | grep 'foo bar' | awk ... Commented Apr 4, 2018 at 16:48
  • All great advice for future efforts, thank you. FWIW, the tail bit came about from efforts to break the pipe down (run the first command, tee and redirect to file, tail that, pipe to next command, redirect to file, etc) and run it continuously in sections. The < is a good tool to keep in mind though. Commented Apr 5, 2018 at 6:59