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

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
  • Comment on Re^11: Net::OpenSSH loosing lines ins reply

Replies are listed 'Best First'.
Re^12: Net::OpenSSH loosing lines ins reply
by salva (Canon) on Jun 04, 2014 at 14:36 UTC
    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.

      Hi Salva,
      I still did not manage to explain the situation:
      /tmp/ssh_del_$$.txt is complete (no line numbers)
      two.out is complete (incl line numbers)
      STDOUT misses a block of lines (see above)

      STDOUT is missing the lines in total - numbers and content.

      I'll continue to cut down the script to the needed fragments for reproducing it...

      not yet giving up...
        STDOUT is missing the lines in total - numbers and content.
        Then, the problem is very likely to be Sig::SigAction breaking some builtin at an inconvenient time and corrupting perl internal state.

        Anyway, running the program with strace may also give some hint.