comment on

Well blow me down, BrowserUK is correct. I've never gotten alarm() to work reliably on Windows - perhaps because I'm not that versed in Signals and didn't know what I was doing or was trying on a system call without the eval/die as described in alarm; however, alarm() added in my original script works:

use strict;
use warnings;

my $pid = open(my $fileHandler, '-|', "./test.exe" );

my $DONE = 0;
$SIG{ALRM} = sub { $DONE = 1 };
alarm 2;

while (<$fileHandler>) {
    print "$_\r"; # \r to not overrun output screen buffer
    last if ($DONE)
}

print "\nTimeout! - Time to kill pid: $pid\n"
[download]

And the output

VinsWorldcom@C:\Users\VinsWorldcom\tmp> TimeThis test.pl

TimeThis :  Command Line :  test.pl
TimeThis :    Start Time :  Fri Oct 12 13:01:09 2012

114601
Timeout! - Time to kill pid: 4700

TimeThis :  Command Line :  test.pl
TimeThis :    Start Time :  Fri Oct 12 13:01:09 2012
TimeThis :      End Time :  Fri Oct 12 13:01:12 2012
TimeThis :  Elapsed Time :  00:00:02.454
[download]

In reply to Re^3: Windows run an exe print its output and cut it off after a time by VinsWorldcom
in thread Windows run an exe print its output and cut it off after a time by anshumangoyal

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.


go ahead... be a heretic
	PerlMonks