I've thought about this overnight and I don't have any good news for you.

If *nix doesn't allow you to control the environment that a child process gets when it is spawned from a thread, that's not the fault of nor can it be influenced or corrected by anything you do in your Perl code.

One alternative I can come up with is that you write your own 'shell' that in addition to doing the require SETs and forking the command, somehow conveys the pid of the forked process back to its parent (your Perl script).

Maybe, it could arrange for the child's pid to be returned as the first line that is read from the pipe?

Another alternative (that I'm barely aware of what might be possible), is to use the memory mapped file structure (is it /dev/...?) to discover the child's pid. I'll leave that idea hanging their cos I don't know enough to know if it is possible or portable.

If you arrive at a solution, please be sure to come back and tell us how you did it, because I can see that it is something others would find useful.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^5: Get the process id, and output of a process, in a threaded environment by BrowserUk
in thread Get the process id, and output of a process, in a threaded environment by rmahin

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.