in reply to Re^8: Net::OpenSSH loosing lines ins reply
in thread Net::OpenSSH loosing lines ins reply

sniplet of STDOUT:
1776: switchport mode trunk 1777: switchport trunk native vlan 1000 1778: switchport trunk allowed vlan 201,221-222 1779: spanning-tree port type edge trunk 1780: storm-control: interface Ethernet8/30 2995: 2996: interface Ethernet8/31 2997: 2998: interface Ethernet8/32 2999: 3000: interface Ethernet8/33 3001: 3002: interface Ethernet8/34 3003:

but two. out contains ALL numbers...

Replies are listed 'Best First'.
Re^10: Net::OpenSSH loosing lines ins reply
by salva (Canon) on Jun 04, 2014 at 13:13 UTC
    but can you use diff to visualize the differences, or even better, some tool as vbindiff.

    update: Include also the diff between ./two.out and the file generated when you use stdout_file to redirect the output to a file.

      Yes, Salva, I can and I did.
      BUT:
      the file is 3500 lines in size and also contains stuff I'll not post here... :-)

      I can send it to you as an eMail - but don't see the value.
      The files are identical, besides the fact that STDOUT has that section missing.

      thanks for your help!!!

      update: /tmp/ssh_del_$$.txt is COMPLETE
      two.out is complete
      STDOUT misses a block of lines
        update: /tmp/ssh_del_$$.txt is COMPLETE

        Ah, from your post Re^2: Net::OpenSSH loosing lines ins reply, I understood "/tmp/ssh_del_$$.txt" was also missing some lines even if the file size was the same!

        if STDOUT were completely empty, I would suspect of Sys::SigAction doing something funny to STDOUT, but you say that the line numbers are there... I can not imagine how that could happen. Is like if $_ were changing from one call to the next?

        You can try reducing the script, first removing Net::OpenSSH from it. You already have the output on the /tmp/ssh_del_$$.txt files, so you don't need to retrieve them again.