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

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


Date: Thu, 22 Feb 2007 12:18:33 -0800
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: kill pgm ?

Content Type: text/plain

Steven Levine wrote:
>
> >1) Since I'm only part way through the dSync mirroring, I'm not in the
> >exit list yet.
>
> There is no way you can say this without some analysis. What does pstat
> say? Exit list functions will run when the application is exiting, unless
> bypassed, anytime an application process is ending, including after an
> exception. It is the responsibility of the exit list routine to protect
> itself against hangs.

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

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?

I suppose I could run pstat >temp.fil before running dSync and then run
pstat >temp.fil2 after dSync hangs, and immediately compare the two temp
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.

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.

The relevant lines from my .cmd are:

dsync -v dsync-NH.cfg
beep dsync-MH.beepdone

No beeps are heard, so I know the screen display didn't freeze while the
program kept running.

- Neuronless Pete

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

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 [ 22 | 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.