Win32::Process ... target problem

[asearle]

Hallo everyone,

After playing around with 'fork' in order to try to get a one process to monitor another, I have changed my tack and switched to Win32::Process. Indeed, it looks like this function will be able to do what I require:

A: Start a windows application
B: While that application is running regularly monitor a log file
C: If the windows application falls over or locks up, then the monitor process will kill the job and close the script cleanly, supplying an error code as return.

However, I am having some issues with the syntax and find that although I can use Win32::Process: :Create to open the program I require (in this test 'notepad'), I find that the target file (here: nptest.txt) will not open. I just get a blank text document.

Here is a sample of my code ...

my $ProcessObj;
Win32::Process: :Create($Proces sObj,
"C:\\WINDOWS\\s ystem32\\notepa d.exe",
"C:\\Temp\\npte st.txt",
0,
NORMAL_PRIORITY _CLASS,
"C:\\Temp") or die ErrorReport();

I have tried all kinds of variations in the path but couldn't get it to open the target file. I find this bizarre as the application itself (notepad and other windows applications) opens fine ... but not the target.

It must be some simple thing that I have missed but I have checked back with examples from the web and I just can't see it. Maybe a second pair of eyes will see what I have missed?

Or maybe you can suggest an alternative command/syntax/process for getting one (repeating) process to monitor another (long) process?

I'd be very grateful for any tips or thoughts that you have.

Regards and thanks,
Alan Searle.

(NB: The double backslashes are necessary otherwise notepad won't open)

[KevinADC]

try using wordpad for the test.

[asearle]

Hi Kevin,

> try using wordpad for the test.

Yes, I tried with wordpad but got the same result: Wordpad opened fine but displayed a blank document (i.e. wouldn't open the target file).

This must be a simple syntax and/or understanding problem on my part and I'd be so grateful if someone could maybe test this on their PC and tell me what they get.

Many thanks,
Alan Searle.

PS: Don't foget you need ...

use Win32::Process;
use Win32;

[KevinADC]

I think the problem here is that the third argument to the Create() method is the commad line arguments you would pass to the process, but there is no command line argument for notepad that enables you to open an existing file. That is why I suggested you try wordpad (Write.exe on my old Win98 test server). This works for me:

my $ProcessObj;
Win32::Process::Create($ProcessObj,
'C:\\WINDOWS\\Write.exe',
'Write.exe temp.txt',
0,
NORMAL_PRIORITY_CLASS,
'.') or die $!;

that opens wordpad and the temp.txt file.

[KevinADC]

I stand corrected (by myself no less) this works as well:

my $ProcessObj;
Win32::Process::Create($ProcessObj,
'C:\\WINDOWS\\notepad.exe',
'notepad temp.txt',
0,
NORMAL_PRIORITY_CLASS,
'.') or die $!;

so your problem might just be in getting all the paths correct.

[KevinADC]

try like this:

my $ProcessObj;
Win32::Process::Create($ProcessObj,
"C:\\WINDOWS\\system32\\notepad.exe",
"[b]notepad[/b] C:\\Temp\\nptest.txt",
0,
NORMAL_PRIORITY_CLASS,
"C:\\Temp") or die ErrorReport();

[asearle]

Yippppeeee! ... it was syntax.

Yes, that fixed the problem ...

> 'C:\\WINDOWS\\n otepad.exe',
> 'notepad temp.txt'

I now know/realize that the name of the program (here notepad) must be included in both the path and in argument where the target file is declared.

Thanks for helping me sort out this problem.

Regards,
Alan.

[asearle]

My testing with Win32 has been moving on and I am happy that I can get my application started. Now I need to be able to detect when the windows application (in my tests, msaccess) has closed.

In my example you can see how I call up msaccess (that works) and then set up a WHILE loop to carry out repeated actions (e.g. read a log file) until the Win32 application closes.

The WHILE loop works OK and (repeatedly) prints out the text 'waiting ...' but, when I close msaccess, the WHILE loop fails to exit. As you can see I am relying on the condition '$ProcessObj.ST ILL_ACTIVE' (I have also tried '$procreturn.ST ILL_ACTIVE').

I have googled on the key words and it seems that 'STILL_ACTIVE' is a valid option for Win32 so there must be something wrong with my syntax.

Any tips here would be a great help.

Regards and thanks,
Alan Searle

Snippet of my code ...

[... other code ...]
my $ProcessObj;
$procreturn=Win 32::Process::Cr eate(
$ProcessObj,
"C:\\mypath\\MS ACCESS.EXE",
"msaccess C:\\anotherpath \\mymdb.mdb",
0,
NORMAL_PRIORITY _CLASS,
".")|| die ErrorReport();

while ( $ProcessObj.STI LL_ACTIVE ) {
# $action = &read_logfile() ;
print "waiting ...\n";
sleep(3);
}

[asearle]

On CPAN I found the following explanation of how to apply the 'STILL_ACTIVE' constant but I am not sure how to incorporate it (with 'GetExitCode' ?) into my processing.

> $ProcessObj->GetExitCode($e xitcode)
> Retrieve the exitcode of the process. Will return STILL_ACTIVE if the
> process is still running. The STILL_ACTIVE constant is only exported by
> explicit request.

Maybe someone has an idea or an example?

Many thanks,
Alan Searle

[KevinADC]

On CPAN I found the following explanation of how to apply the 'STILL_ACTIVE' constant but I am not sure how to incorporate it (with 'GetExitCode' ?) into my processing.

> $ProcessObj->GetExitCode($e xitcode)
> Retrieve the exitcode of the process. Will return STILL_ACTIVE if the
> process is still running. The STILL_ACTIVE constant is only exported by
> explicit request.

Maybe someone has an idea or an example?

Many thanks,
Alan Searle

maybe:

while($ProcessObj->GetExitCode($exitcode)  eq 'STILL_ACTIVE') {

[asearle]

Hi Kevin,

Yes, your suggestion seems logical and so I tried ...

while($ProcessO bj->GetExitCode($e xitcode) eq 'STILL_ACTIVE') { [...]
while($ProcessO bj->GetExitCode($e xitcode) eq STILL_ACTIVE) { [...]
while($ProcessO bj->GetExitCode($e xitcode) == STILL_ACTIVE) { [...]

... and found that with this the process immediately exits the loop and ends while my windows application remains/is still active.

I tried once again to see what values GetExitCode returns and so re-activated the loop and got the system to print out the PID and the ExitCode these remain the same (ExitCode: 1) even after the application is closed. So there is something that I am not picking up.

I have googled a lot (really a lot!) and found information on CPAN but they don't seem to explain how to detect the ending of the process.

Anyway, many thanks for your tip: It looks plausible/correct (a colleague also suggested something similar) and so I'm even more bemused as to why it doesn't work.

Thanks,
Alan.

[KevinADC]

use Win32::Process qw(STILL_ACTIVE);

if ($ProcessObj->GetExitCode($exitcode) eq 'STILL_ACTIVE') {
   do something
}

[asearle]

Hi Kevin,

Thanks so much for your help/tips. But 'use Win32::Process qw(STILL_ACTIVE );' also didn't help :-/

I have reduced my code to the absolute minimum with the goal of getting the process to detect when wordpad closes.

With Version 'A', I get an endless loop and with 'B' (your suggestion) I find that the WHILE loop exits immediately. I have included debug prints of PID and exit code (which display with Version 'A').

Maybe, if you have a spare moment, you could try to run it to see what you get?

Thanks very much,
Alan Searle

My Code ...

use Win32::Process;
use Win32::Process qw(STILL_ACTIVE );
use Win32;
#
print "Starting\n ";
sleep(1);
my ($ProcessObj, $exitcode);
Win32::Process: :Create($Proces sObj, "C:\\Progra m\ Files\\Windows\ NT\\Accessories \\wordpad.exe",
"wordpad C:\\Temp\\temp. txt",
0,
NORMAL_PRIORITY _CLASS,
".") || die ErrorReport();
# Version A: endless loop ...
# $ProcessObj.STI LL_ACTIVE
# Version B: exits loop immediately ...
# $ProcessObj->GetExitCode($e xitcode) eq 'STILL_ACTIVE'
while ($ProcessObj->GetExitCode($e xitcode) eq 'STILL_ACTIVE') {
# $action = &read_logfile() ;
print "Waiting ... \n";
# print "Process waiting ", $ProcessObj->wait(INFINITE) , "\n";
print "Process started with PID ", $ProcessObj->GetProcessID() , "\n";
print "Process completed with exit code ", $ProcessObj->GetExitCode( $exitcode ), "\n";
sleep(3);
}
print "ending\n";
sleep(4);

[KevinADC]

well, according to the documentation you have to import the STILL_ACTIVE constant:

The following additional constants are exported by request only:

STILL_ACTIVE

use Win32::Process qw(STILL_ACTIVE);
    use Win32;

    Win32::Process::Create($ProcessObj,
                                "C:\\winnt\\system32\\notepad.exe",
                                "notepad temp.txt",
                                0,
                                NORMAL_PRIORITY_CLASS,
                                ".")|| die ErrorReport();

    my $status = $ProcessObj->GetExitCode($exitcode);
    if ($status eq 'STILL_ACTIVE') {
       print "still running\n";
    }

[asearle]

Hi Kevin,

> well, according to the documentation you have to import the STILL_ACTIVE
> constant:
> use Win32::Process qw(STILL_ACTIVE );

Yes, I see you doing that. And have incorporated this.

And I see you testing for the exitcode ...

> my $status = $ProcessObj->GetExitCode($e xitcode);
> if ($status eq 'STILL_ACTIVE') {

... and I have also done a debug print on the exit code thus ...

print "Process completed with exit code ", $ProcessObj->GetExitCode( $exitcode ), "\n";

... and incorporated this into my background loop. However, the exitcode is always '1' both while the application is open and after it is closed down. Is this just the exit code for the action of opening the external application? I was expecting it to change when I close down wordpad (or notepad). But it doesn't.

I haven't been working with perl for so long and I think maybe I have a hole in my understanding: If GetExitCode() is always returning the same value (during and after the running of the application), then comparing it to the constant STILL_ACTIVE will make no difference (will it?).

I am a bit out of my depth here but I really do need to get a looping process to monitor the progress of the windows application and here I seem to be just soooooo close to working it out.

Many thanks for your patience.

Regards,
Alan.