ok ..thanks for your help.
I made the parent wait for the forked process, after the forked process had been killed. The parent was able to receive the PID of the process that had already been killed using: kill -9 <PID>.
The fact that parent received the PID of the killed child indicates that the parent must actually wait for a killed process as well ..only then would the resources consumed by the child process would be freed (ex. Entry in the process table etc.)

Please let me know in case I am missing anything here ....Thanks again!

In reply to Re^2: Does a parent need to wait on a child killed using SIGKILL? by piyush
in thread Does a parent need to wait on a child killed using SIGKILL? by piyush

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.