G'day srlbharu,

I'm not entirely certain what you're trying to achieve here. Sending a negative signal targets a process group not an individual process. To terminate the current process, you can just use die, exit or one of the Carp routines.

I suspect you're lacking knowledge or understanding of one or more of the following. (Also note that many of these contain links labelled "Portability issues:".)

• fork
• kill
• alarm
• waitpid
• perlipc

$child_pid = $$;

$$ is not the child process identifier. You have the parent process trying to kill itself.

But, more fundamentally, fork does not work properly on Windows; and you are wasting your time writing new code that tries to use it.

Yes I agree, But I know only one way to create the child to run it parallel to parent in perl 5.6 using fork

Trying to upgrade the perl version leads to lot of compatibility issues so that I stopped my trails to upgrade

Here I am getting the error: "Attemt to free uneferenced scalar" with perl 5.6 while exiting the child process and then terminating the parent process also. Hence I keep the child in infinite loop and once the parent is going to be completed I want to kill the child by sending signal like CTRL+C

I tried the ways like die, exit, Win32::Process::Killprocess and kill 9,$pid; to kill the child no use

But I know only one way to create the child to run it parallel to parent in perl 5.6 using fork

If all you want it to run an asynchronous process, try my $childPid = system 1, q[theCommand and args];.

But don;t expect much help if you run into problems. On 5.6, you are on your own. Noone wants to be bothered trying to re-debug code that has long since been fixed.

---

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.