HP3000-L Archives

December 1999, Week 5

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:
"Stigers, Greg [And]" <[log in to unmask]>
Reply To:
Stigers, Greg [And]
Date:
Wed, 29 Dec 1999 18:15:48 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
X-no-Archive:yes
Is the kill intrinsic is anything like the kill command? Big brother MPE
will not allow me to kill pids that are not running under the same id as the
kill command, unless you have SM capability, which in my opinion is a bad id
from which to discover an error in one's kill scripts... Nonetheless, this
restriction is one reason MPE is so stable! There was quite the discussion
of this on list some months ago.

Say I am running the apache daemon in a job under server.apache, and now I
want to kill its pid. I can stream a job, running under server.apache, and,
even though the two jobs have no real parent, child, or sibling
relationship, I can read the ./logs/httpd.pid for the pid, and then kill the
pid.
!JOB HTTPSTOP,SERVER.APACHE
!#After editing, ALTSEC HTTPSTOP.PUB.APACHE;NEWACD=(X:OPERATOR.SYS)
!INPUT PID<./logs/httpd.pid
!XEQ SH.HPBIN.SYS "-c 'kill !PID'"
!EOJ

Or, say I am the operator, and want to bring down the samba daemon. I can
sign on as mgr.samba, ps -A (which is broken in a way that causes it fail in
a job stream), find the samba daemon's pid, and kill it.

Greg Stigers
http://www.cgiusa.com

ATOM RSS1 RSS2