Thanks for the pointer on how to handle the paged output. I will definitely give this a try but my preference would be to process the entire command output with paging disabled on the server.
What I meant by 'choking' is that I am seeing a premature close on the stream when the output exceeds approx. 400 lines. Smaller output sizes seem to complete reliably and I can parse the entire command output without any troubles. I am seeing the following logs to console based off some of the examples posted on github: Stream :: exit :: code: 1, signal: undefined Stream :: close Hoping you can spot what i am missing in my setup on the ssh2 client below. https://gist.github.com/anonymous/b0f7f71e9c7db08b48cc On Thursday, October 9, 2014 5:11:13 AM UTC-7, mscdex wrote: > > On Wednesday, October 8, 2014 8:55:43 PM UTC-4, cesdaile wrote: >> >> >> I attempted to set the server to not page but I am finding the ssh2 >> client is choking on the output when there is more than 500 lines being >> returned so I am reconsidering going interactive and trying to page through >> the data as required. >> >> > Can you explain what you mean by "choking on the output"? This gist[1] > works for me. > > [1] https://gist.github.com/anonymous/3954981240f92b2df32b > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/64f11c80-4b7d-48f4-a91b-0e4ec06d9656%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
