Hello,
How do I test, from a program, if some other process is running given
its process ID (PID)?
The external process is started with DosStartSession() and returns the
process ID since SSF_RELATED_CHILD is indicated. Unfortunately,
DosWaitChild() always returns ERROR_WAIT_NO_CHILDREN regardless of the
existence of the external process. I can see no obvious (to me) kernel
function that gives information about other processes.
> How do I test, from a program, if some other process is running given
> its process ID (PID)?
It depends on how you started the program.
> The external process is started with DosStartSession() and returns the
> process ID since SSF_RELATED_CHILD is indicated. Unfortunately,
> DosWaitChild() always returns ERROR_WAIT_NO_CHILDREN regardless of the
> existence of the external process.
TTBOMK, you are mis-using DosWaitChild. Note that the remarks say that DosWaitChild is used to detect completion of programs started by DosExecPgm.
To monitor session completion, use a termination queue. You can also use DosQuerySysState, but this is a bit of a hack.
Steven
-- ---------------------------------------------------------------------
Steven Levine <stev...@earthlink.bogus.net>
eCS/Warp/DIY etc. www.scoug.comwww.ecomstation.com ---------------------------------------------------------------------
<jimoeDES...@sohnen-moe.com> wrote:
> Hello,
> How do I test, from a program, if some other process is running given
> its process ID (PID)?
> The external process is started with DosStartSession() and returns the
> process ID since SSF_RELATED_CHILD is indicated. Unfortunately,
> DosWaitChild() always returns ERROR_WAIT_NO_CHILDREN regardless of the
> existence of the external process. I can see no obvious (to me) kernel
> function that gives information about other processes.
BIt of a hack but you could do a popen() of PSTAT and parse the output.
>> The external process is started with DosStartSession() and returns the
>> process ID since SSF_RELATED_CHILD is indicated. Unfortunately,
>> DosWaitChild() always returns ERROR_WAIT_NO_CHILDREN regardless of the
>> existence of the external process.
> TTBOMK, you are mis-using DosWaitChild. Note that the remarks say > that DosWaitChild is used to detect completion of programs started by > DosExecPgm.
Oops. Missed that part.
> To monitor session completion, use a termination queue. You can also > use DosQuerySysState, but this is a bit of a hack.
On Sun, 16 Sep 2012 10:37:10 UTC, "Dave Saville" <d...@invalid.invalid> wrote:
> > How do I test, from a program, if some other process is running given
> > its process ID (PID)?
> > The external process is started with DosStartSession() and returns the
> > process ID since SSF_RELATED_CHILD is indicated. Unfortunately,
> > DosWaitChild() always returns ERROR_WAIT_NO_CHILDREN regardless of the
> > existence of the external process. I can see no obvious (to me) kernel
> > function that gives information about other processes.
> BIt of a hack but you could do a popen() of PSTAT and parse the > output.
More than a bit... if that's the approach you want to take, it'd be far more efficient to get a process list directly using DosQuerySysState().
>> The return code, rc, is always ERROR_INVALID_PARAMETER (87). But I do
>> not see which parameter is invalid.
> You have to supply a semaphore handle with DCWW_NOWAIT according to CPREF.
> Read the Remarks page for DosPeekQueue.
Thank you.
I did read the Remarks for DosPeekQueue(). The part about nowait and a
semaphore made it seem that the semaphore was optional.
I modified the code to use DCWW_WAIT instead, without a semaphore. The
function never returned even after the external process ended. The
process did end badly; I ended it by sending an interrupt via a process
killer.
Would a process ending that way fail to place anything in the
termination queue? I rather had the impression that the OS handled that
part of it, not the ending process.
for an implementation. It's probably a bit more complicated than James needs because it handles a large number of application types.
Steven
-- ---------------------------------------------------------------------
Steven Levine <stev...@earthlink.bogus.net>
eCS/Warp/DIY etc. www.scoug.comwww.ecomstation.com ---------------------------------------------------------------------
On Sun, 16 Sep 2012 04:01:01 UTC, James Moe wrote:
> How do I test, from a program, if some other process is running given
> its process ID (PID)?
> The external process is started with DosStartSession() and returns the
> process ID since SSF_RELATED_CHILD is indicated. Unfortunately,
> DosWaitChild() always returns ERROR_WAIT_NO_CHILDREN regardless of the
> existence of the external process. I can see no obvious (to me) kernel
> function that gives information about other processes.
As always, no one has asked the fundamental question: "why are you using
DosStartSession() in the first place"? It may be the correct solution for
the issue at hand - or its use could be totally boneheaded. I don't see
how helping someone do the wrong thing is genuinely helpful.
So... what app is calling DosStartSession()? (PMMail, I'd guess.)
What program is it starting? Are you positive that it needs a new session?
Does your app (or some functionality therein) have to block until this
mystery process terminates? Etc, etc.
Also, have you considered using WinStartApp()?
-- == == almost usable email address: Rich AT E-vertise DOT Com == ==
> So... what app is calling DosStartSession()? (PMMail, I'd guess.)
> What program is it starting? Are you positive that it needs a new session?
> Does your app (or some functionality therein) have to block until this
> mystery process terminates? Etc, etc.
Yes, PMMail.
It is starting stunnel, a security proxy. Stunnel provides encrypted
data transfer for PMMail.
It originally used DosExecPgm() to start stunnel. DosStartSession()
can start a program without inheriting the current environment and file
handles. It was more of a debugging effort to eliminate a possibility
than any actual advantage of DosStartSession(). I then wanted to know if
the program was actually running, or be notified when it quit. Hence the
posting.
(The problem I am having is with files being closed but randomly
unavailable, sometimes for many seconds. For instance, a file is
created, written, closed, all with standard C functions. That file may
then be copied to another file, or renamed. In either case, sometimes
the copy/rename returns error 13, Permission Denied.
The last time I had a similar problem was when an external program was
started that inherited file handles, and closed those inherited handles
when it quit. The parent process was not pleased.)
On Wed, 19 Sep 2012 10:28:53 -0700, James Moe <jimoeDES...@sohnen-moe.com>
wrote:
> The last time I had a similar problem was when an external program was
> started that inherited file handles, and closed those inherited handles
> when it quit. The parent process was not pleased.)
All programs close all file handles when they exit. The child closing
its handles has no effect on those of the parent.
Your analysis is flawed somewhere.
