Re: Re: Re: Re: perl fork cmd on Windows 2000

Thanks for ur suggestion. Win32::process works fine in creating a process, but does it work the same way as a thread..?

Actually, I am looking for a way to call another perl script file from a script, so the called script will run on the background.To be more specific, even if the file(called-script) i am calling leads to a infinite loop, the calling-script must continue executing...

Is it possible to do this using Win32::Process ? Does anyone know how to go about it ?

Comment on Re: Re: Re: Re: perl fork cmd on Windows 2000

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: perl fork cmd on Windows 2000 by BrowserUk (Patriarch) on Dec 18, 2002 at 05:59 UTC
You can use Win32::Process to start a second copy of Perl as a seperate process, and run the second script there if that will fulfill your requirements. You can specify DETACHED_PROCESS when you call Win32::Process:Create(...); which will deal with that part. What you haven't said so far is whether you want the ability for the 2 scripts to communicate. You can do this with either Win32::Pipe or sockets. You also haven't said whether you need to actively kill the background process in the event that it goes ary or runs too long. Win32::Process::KillProcess() or $pid->Kill(); will take care of the first part if needed and then you only have to decide when. Whether by timing or some other mechanism, but more details on your requirements would help. Examine what is said, not who speaks.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Re: perl fork cmd on Windows 2000
by BrowserUk (Patriarch) on Dec 18, 2002 at 05:59 UTC

You can use Win32::Process to start a second copy of Perl as a seperate process, and run the second script there if that will fulfill your requirements. You can specify DETACHED_PROCESS when you call Win32::Process:Create(...); which will deal with that part.

What you haven't said so far is whether you want the ability for the 2 scripts to communicate. You can do this with either Win32::Pipe or sockets.

You also haven't said whether you need to actively kill the background process in the event that it goes ary or runs too long. Win32::Process::KillProcess() or $pid->Kill(); will take care of the first part if needed and then you only have to decide when. Whether by timing or some other mechanism, but more details on your requirements would help.

Examine what is said, not who speaks.

[reply]