Hi, I have a slightly modified version of ExecuteProcess that's been customized to do various "find targetdir -print" style commands, which generates standard output that results in a FlowFile. Large outputs (long directory listings of 100 lines or more) work perfectly; however, it appears that brief outputs from find to stdout (e.g., 8 to 10 lines) are not being picked up at all (the FlowFile length is zero after the find command runs). In the debugger I can see the find command is properly formed, then after it runs the FlowFile is zero bytes in length.
I suspect this is some kind of issue with stdout not being flushed sufficiently by "find" to be picked up as input, but not sure at this point. The process flow is a bit of a mystery at this point, so wondering if anyone might shed some light on how to troubleshoot/resolve (this most likely happens on a standard ExecuteProcess processor, but haven't tried to reproduce it on that processor yet). Rick
