HP3000-L Archives

December 1997, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Thu, 18 Dec 1997 19:18:16 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Various people mentioned hybrid MPE/Posix solutions, I have one (well,
at least a technique) that I used today to solve a particularly nasty
problem.

I have a background job that manages a big process-handling application
that became "hung" today for no obvious reason.  Using :abortjob did not
logoff the job, and more mysteriously ":showproc;job=#Jnnn" came up with
the "no matching job/session found" and listed no processes.  Yet it was
still in :showjob.

From the shell, I tried "ps -ef|grep 'user.acct'" and it gave me a
process or two but not all.  Then "callci 'showq'|grep '#Jnnn'" did
indeed spit out the pins of the remaining processes.  Using :debug
with the 'pin #nnn;tr,i,d' mentioned a few days ago showed the programs
were in FLOCK.  The new :listfile,locks yielded the owner of the lock
and a solution to the problem (just when it looked like a reboot was
in order).  Case closed!

When you have 300-400 processes active, it sure beat the heck out of
scanning down a regular :SHOWQ for the job number and associated pins!

In retrospect of my recent HPUX force-feeding, I would encourage the
non-Posix reader to start with 'grep' as I find it an increasingly
indispensible tool, especially from the shell when you can easily pipe
programmatic output into it, or use shell wildcards in filenames.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2