I'm not even sure what signal I should be sending with the kill

Windows has two signals, Ctrl-C and Ctrl-Break. It uses message passing primarily, but that's for application with Windows. It can terminate processes forcibly.

I think you can send the Ctrl-C and Ctrl-Break signals using kill, but I don't know which numbers do this.

kill 9 surely results in the the system call to terminate a process. That's drastic.

BUT it does not kill the gzip or mycommand processes when it gets to the "kill 9, $pid".

It kills the shell whose pid is in $pid. This doesn't kill the shell's children. I don't know one would achieve that.

One solution would be to eliminate the shell and do the piping yourself.


In reply to Re: open (to read) and kill a pipe to a pipe by ikegami
in thread open (to read) and kill a pipe to a pipe by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.