Run multiple processes and wait for them

[SHAHRAM]

Hello,

I am using "PSEXEC" to run some software on a couple of remote computers at the same time and know when they are closed so my application can continue,

My problem is if I used "RunWait", it goes from one client to another waiting for each to finish before going to the next

and if I used "Run", I can execute them simultaneously but my application cant wait for them,

so my question is, is it possible to run a couple of "RunWait"s at the same time.

[PsaltyDS]

Run() returns the PIDs, and you can use those to track when the processes close.

[SHAHRAM]

Run() returns the PIDs, and you can use those to track when the processes close.

thanx, I have been playing with it a little bit,

running psexec is usually like "@ComSpec & ' /c psexec.exe ...'"

so Run() returns pid of the cmd.exe on the local computer and not the remote process,

but at the end I was able to use the "-d" switch on psexec which is "Don't wait for application to terminate" and then use RunWait() on it,

this ways, psexec returns the process id as %errorlevel% which RunWait() catches,

then using similar concept, process id can be passed to "PSLIST", and from the returned errorlevel I can see if the process was closed or not.

[PsaltyDS]

The @COMSPEC shell is only required to run native shell commands (i.e. DIR). You should be able to run PSEXEC.exe directly without the @COMSPEC.

[SHAHRAM]

Well, its working this way for, though I dont think Run() would give me the PID of the Remote Process if psexec is executed directly.

RunWait() is very convenient that it waits for psexec to finish with running the remote program and then catches the PID which was returned as ERRORLEVEL (exit code),

There is one problem with RunWait() though in this case,

Is there any ways to capture the output of psexec from RunWait() inside autoit???????????????????

(right now the only thing I can do is to output it to a file ("2> x.log") and read the content of that file)

PS.

Explanation of why it is needed

when psexec fails, it returns a windows error code instead of PID, for example "1326" for logon failure,

but there is no way for me to know if this number is a PID or an error code,

If I could get STDOUT of RunWait() the problem would be solved

(I can look a word that identifies it as success eg "started", otherwise treat it as failure)

But it seems "$STDERR_CHILD / $STDOUT_CHILD" only work with streams coming from Run() and I cant find any functions that captures output of RunWait(),

[Gianni]

......

Is there any ways to capture the output of psexec from RunWait() inside autoit???????????????????

(right now the only thing I can do is to output it to a file ("2> x.log") and read the content of that file)

......

use RemCom.exe instead of psexec....see here:

I used it and it works well

bye

[jdelaney]

You can always use TCPIP connections...or, have the called station create a text file of the current status on a shared drive, and have your caller check periodically for updates/completion.