HP3000-L Archives

June 1999, 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:
"Stigers, Greg [And]" <[log in to unmask]>
Reply To:
Stigers, Greg [And]
Date:
Wed, 16 Jun 1999 12:30:00 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines)
X-no-Archive:yes
SR 4701-426643 requests that ps work in batch for non-SM users. If this
matters to you, practically or just philosophically (shell components should
work as expected), please jump on this bandwagon.

I previously mentioned problems with using ps in batch, and that MPEJXH5A,
which is in beta, will allow ps in batch, with one important limitation. The
user under which it runs must have SM capabilities. I am reluctant to kill
pids under a user with SM capabilities. For instance, a scripting error
could kill the wrong pid(s), among other concerns. I could use hack-arounds
to mitigate this risk, having one job run under manager.sys to create a
listing with ps -A>PSLIST (and saving it), and other appropriate jobs run
under FTP.SYS or MGR.SAMBA read this file, for instance, but that is
needlessly complicating something simple.

I understand that MPE 65 should have a normal ps, and that we could see a
patch for 60 and 55 before 65 ships. I also understand that HP is looking at
providing jobs to cleanly bring down these various daemons by appropriate
means in future releases.

ATOM RSS1 RSS2