SCOUG-HELP Mailing List Archives
Return to [ 28 |
March |
2004 ]
<< Previous Message <<
>> Next Message >>
Date: | Sun, 28 Mar 2004 09:17:57 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.
=====================================================
Harry Motin wrote:
>
> Timing is the issue, I think.
The possible failure scenario that keeps nagging at me is that some
other process might start a .cmd at the same time. This is unlikely
except at startup, but startup is when my logging and monitoring
routines will all start. Your idea of polling the PID list is a good
one and as long as there is only one new CMD shown then there isn't any
confusion; I will just have to check to make sure there aren't multiple
new CMDs.
Thanks, Harry.
- 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".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 28 |
March |
2004 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
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.
|