Re^5: Shared memory and asynchronous access

i didnt try yours till now cuz you used system, i wanted to see how the fork ran on win. Yours worked fine. Your $pid is positive rather than the negative one from the perlfork version and is a real pid that kill can watch ok. the $pid from perlfork is negative, an pseudo-pid, and it seems kill didnt think it was "done" till the waitpid call ran.

Comment on Re^5: Shared memory and asynchronous access

Replies are listed 'Best First'.
Re^6: Shared memory and asynchronous access by BrowserUk (Patriarch) on Apr 06, 2017 at 10:51 UTC
the $pid from perlfork is negative, an pseudo-pid, and it seems kill didnt think it was "done" till the waitpid call ran. Okay. Thanks for the explanation. I was confused about what was going on there for a while. 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". The enemy of (IT) success is complexity. In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]

Replies are listed 'Best First'.

Re^6: Shared memory and asynchronous access
by BrowserUk (Patriarch) on Apr 06, 2017 at 10:51 UTC

the $pid from perlfork is negative, an pseudo-pid, and it seems kill didnt think it was "done" till the waitpid call ran.

Okay. Thanks for the explanation. I was confused about what was going on there for a while.

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". The enemy of (IT) success is complexity.

In the absence of evidence, opinion is indistinguishable from prejudice.

[reply]