SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Sat, 27 Mar 2004 09:02:50 PST8PDT,4,1,0,3600,10,-1,0,7200,3600
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: killing one of several .cmd files

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven Levine wrote:
>
> The standard solution is for the .cmd file to
> record it's PID somewhere, usually in a file
> with a name corresponding to the script name.

So AAA.cmd has its PID in the AAA.pid file, yes?

And if you have AAA.cmd running simultaneously in two different windows,
then the AAA.pid file contains two lines with the two different PIDs,
yes?

> It's even easier if you use a capable shell that
> will tell you the PID of an app when you start it.

Hmm. I can START a shell and give it a .cmd to execute, and that .cmd
can start my AAA.cmd file. In other words, using some shell that lets
you stash the PID somewhere (probably some syntax errors in the
following)

start someshell.exe /c startAAA.cmd

where startAAA.cmd is

start /pidfile=AAA.pid /c AAA.cmd
exit

Thus someshell.exe starts up, starts AAA.cmd, and exits. AAA.cmd is now
running. And AAA.pid contains the PID for AAA.cmd.

So I need someshell.exe which has /pidfile= capability. Know of
anything?

Alternately, I need a WhatsMyPID.exe file which I can run at the
beginning of each of my .cmd files.

Maybe I'll just make a bunch of cmd.exe copies named cmd-AAA.exe etc.
Then I'll use cmd-AAA.exe to start AAA.cmd etc. And my PSTAT /C list
will then be very clear as to which PID goes with which .cmd.

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 27 | March | 2004 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.