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.