ELISHEVA: I think you have made a mistake. exec() on it's own will replace the currently running perl process with the new program, so a sucessfull call to exec will never return.
Perhaps you are thinking of a fork/exec or one of the many inter process comumnication methods described in perlipc.
To answer the original question, it depened on what shayak means by 'stops responding' Assuming that he can deduce that, then I would say the simplest method would be to start the process with open or fork/exec eg:
my $child_pid = open $handle, '-|', '/path/to/program' or die "Error s
+tarting program $!";
# Some time later the program stops responding
kill($child_pid);
or:
my $child_pid = fork();
if( 0 == $child_pid )
{
# Child
exec '/path/to/program';
die "error starting program $!";
}
# Some time later the program stops responding
kill($child_pid);
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|