Re: survive with exec

2006-02-27 Thread a b
Hello, The Os was windows and use of start along with system is working fine. Thanks & Regards a b On 2/28/06, Timothy Johnson <[EMAIL PROTECTED]> wrote: > > > What operating system are you running, and how important is the return > code to you? > > If you are using Windows, for example, you can

RE: survive with exec

2006-02-27 Thread Timothy Johnson
What operating system are you running, and how important is the return code to you? If you are using Windows, for example, you can use the start or call commands along with system() to spawn a process and immediately return. The only problem is that you won't be able to check the return code, bec

Re: survive with exec

2006-02-27 Thread Jeff Pang
>exec ("wperl hang.pl >a.txt"); >exec ("wperl hang.pl >b.txt"); >exec ("wperl hang.pl >c.txt"); and,I'm a little strange here. if your first 'exec' is executed successfully,the main script process should be replaced with the exec call.In other words,the executing of 'wperl hang.pl >a.txt' shoul

Re: survive with exec

2006-02-27 Thread Jeff Pang
>exec ("wperl hang.pl >a.txt"); >exec ("wperl hang.pl >b.txt"); >exec ("wperl hang.pl >c.txt"); > hi, here I think you could fork the childs,and call the 'exec' in childs,it should be good for your purpose. for example, for (my $i=0;$i<3;$i++){ my $child = fork();die "can't fork $!" unless

Re: survive with exec

2006-02-27 Thread Bob Showalter
a b wrote: Here i want to execute one and then execute another but don't wait for previous command i.e.something in background but im unable to do it. see: perldoc -q 'How do I start a process in the background?' -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail