HP3000-L Archives

December 2000, 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:
John Burke <[log in to unmask]>
Reply To:
John Burke <[log in to unmask]>
Date:
Wed, 20 Dec 2000 12:21:23 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (80 lines)
Here is what I get for my Apache job on one system (looking at the process
tree in two different ways):

<SASHA: JPB,MGR.SYSADMIN,PUB> WED, DEC 20, 2000 12:05 PM  </SYSADMIN/PUB>
[18]:showproc ![jinfo("#j25","jsmainpin")];tree;system
QPRI  CPUTIME   STATE  JOBNUM  PIN  (PROGRAM) STEP

B152  0:00.335  WAIT   J25     73   (JSMAIN.PUB.SYS)
C152  0:00.425  WAIT   J25       61   :RUN HTTPD;info='-f
/APACHE/PUB/conf/htt$
C200  00:36:40  WAIT   J25         78   (HTTPD.PUB.APACHE) -f
/APACHE/PUB/conf$
C152  0:00.650  WAIT   J25           54   (HTTPD.PUB.APACHE)
C152  0:00.901  WAIT   J25           89   (HTTPD.PUB.APACHE)
C152  0:00.637  WAIT   J25           53   (HTTPD.PUB.APACHE)
C152  0:00.829  WAIT   J25           52   (HTTPD.PUB.APACHE)
C152  0:00.838  WAIT   J25           71   (HTTPD.PUB.APACHE)
C152  0:00.061  WAIT   J25           57   (HTTPD.PUB.APACHE)
C152  0:00.703  WAIT   J25           68   (HTTPD.PUB.APACHE)
C152  0:00.044  WAIT   J25           34   (HTTPD.PUB.APACHE)
<SASHA: JPB,MGR.SYSADMIN,PUB> WED, DEC 20, 2000 12:05 PM  </SYSADMIN/PUB>
[19]:ps '-au WWW.APACHE'
       PID TTY      TIME COMMAND
   4128802 ldev10   0:00 HTTPD.PUB.APACHE
   2031668 ldev10   0:00 HTTPD.PUB.APACHE
    524341 ldev10   0:00 HTTPD.PUB.APACHE
    524342 ldev10   0:00 HTTPD.PUB.APACHE
  59375673 ldev10   0:00 HTTPD.PUB.APACHE
  33161277 ldev10   0:00 CI.PUB.SYS
   3276868 ldev10   0:00 HTTPD.PUB.APACHE
  35389511 ldev10   0:00 HTTPD.PUB.APACHE
   6029390 ldev10  36:40 HTTPD.PUB.APACHE info=-f
   4980825 ldev10   0:00 HTTPD.PUB.APACHE
<SASHA: JPB,MGR.SYSADMIN,PUB> WED, DEC 20, 2000 12:05 PM  </SYSADMIN/PUB>
[20]:

You can match up PINs and PIDs by looking at the rightmost 16 bits of the
PID, which will equal the PIN. For example:

calc(6029390)
6029390, $5C004E, %27000116

and 4E(16)=78(10).

John Burke

> -----Original Message-----
> From: Donna Garverick [mailto:[log in to unmask]]
> Sent: Wednesday, December 20, 2000 11:52 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] PX2LXD4(A)
>
>
> Ted Ashton wrote:
>
> > Thus it was written in the epistle of Donna Garverick,
> > > my entirely non-scientific observations indicate that
> 'smallish' pids (in the
> > > 65k range) are the right number.  'large-ish' pids (like
> 196758 in the above
> > > example) are...well not :-)
> >
> > Here, killing the smallest of the pids is generally the way
> to go because the
> > others are all children of the first and will go away when it does.
>
> that's what i figured....          - d
>
> --
> Donna Garverick     Sr. System Programmer
> 925-210-6631        [log in to unmask]
>
> "Unix _is_ user friendly.
> It's just very selective about who its friends are.
> And sometimes even best friends have fights."
>
> >>>MY opinions, not Longs Drug Stores'<<<
>
>

ATOM RSS1 RSS2