SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 26 | March | 2004 ]

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


Date: Fri, 26 Mar 2004 17:54:01 PST8PDT,4,1,0,3600,10,-1,0,7200,3600
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: killing one of several .cmd files

===================================================== 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. ===================================================== In <20040327000018.27861.qmail@web80203.mail.yahoo.com>, on 03/26/04 at 04:00 PM, Harry Motin said: > 3. What he does is first get all of the process ID's before starting >any of the *.cmd programs Your method will all work, but it's really roundabout and it is subject to interesting failure modes. 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. This makes the solution really simple. It's even easier if you use a capable shell that will tell you the PID of an app when you start it. This way, you don't need to duplicate the code to record the PID in every .cmd file. Regards, Steven -- ---------------------------------------------------------------------- "Steven Levine" MR2/ICE 2.41 #10183 Warp4/FP15/14.093c_W4 www.scoug.com irc.webbnet.info irc.fyrelizard.org #scoug (Wed 7pm PST) ---------------------------------------------------------------------- ===================================================== 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 [ 26 | 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.