Lines Matching full:stderr
30 Or: can you explain me the story about the shared stdout/stderr window in the SSH-2 protocol?
77 session. Be prepared to consume stdout and stderr data.</li>
132 Or: can you explain me the story about the shared stdout/stderr window in the SSH-2 protocol?
141 Unfortunately, the SSH-2 protocol defines a shared window for stderr and stdout. As a consequence,
142 if, for example, the remote process produces a lot of stderr data and you never consume it, then after
145 cannot send you any, since the receive window is full (you would have to read some stderr data first
165 <li><b>Bad: Do nothing</b> - just work with stderr and stdout Inputstreams and hope that the 30KB
169 and stderr in parallel. Since you probably are not in the mood to program such a thing, you can use
174 InputStream stderr = new StreamGobbler(mysession.getStderr());</pre></b></tt>
175 You then can access stdout and stderr in any order, in the background the StreamGobblers will
181 or stderr data has arrived and can be consumed with the two InputStreams. You can either use the return value
183 (for stdout and stderr) which InputStream has data available (i.e., a <tt>read()</tt> call will not block).
188 <li><b>The lazy way:</b> you don't mind if stdout and stderr data is being mixed into the same
189 stream. Just allocate a "dumb" pty and the server will hopefully not send you any data on the stderr
215 InputStream stderr = new StreamGobbler(mysession.getStderr());
