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 [ 23 | February | 2007 ]

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


Date: Fri, 23 Feb 2007 01:52:36 -0800
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: kill pgm ?

In <45DDE824.50E7@peterskye.com>, on 02/22/07
at 12:18 PM, Peter Skye said:

>pstat /c doesn't help much when I have about 30 CMD's running, one of
>which contains dSync.

There's a number of simple solutions to this problem. Your wrapper
scripts could write the PID to a file. I do this on the SCOUG server to
keep track of the REXX deamons. For one-off analysis, Theseus can show
you the command lines. IAC, you are not looking for cmd.exe instances,
you are looking for dSync instances. How many of these do you have
running?

>But I don't quite follow your lead here -- I thought pstat /c would show
>a program if it is hung in the exit list and it also will show a program
>that is hung but hasn't exited yet, so what do I learn from running
>pstat?

If you have more than one dSync instance running, you should be able to
figure out which instances are still getting useful work done and which
are not.

Since you seem to be implying that you have multiple dSync instances
running, you'll probably need to use Theseus to sort this out unless you
are willing to let the other dSync instances finish. Then the one that's
left is the one that's stuck.

>files to figure out which CMD.EXE is running dSync. But I don't
>understand how this will tell me if dSync (or its calling CMD.EXE) is
>stuck in the exit list.

If the dSync instance is not doing useful work, it's very likely stuck in
the exit list. Cmd.exe is brain-dead, but experience says it's unlikely
to get stuck in the exit list.

>dSync displays the current filename being processed. The screen shows
>dSync stopped part way through the file tree. Thus it is likely that
>dSync isn't in the exit list yet.

If the dSync instance is still running, it's very likely it's stuck in the
exit list.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #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
"postmaster@scoug.com".

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


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

Return to [ 23 | February | 2007 ]



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.