HP3000-L Archives

December 2000, Week 1

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:
Tue, 5 Dec 2000 15:31:10 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
X-no-Archive:yes
Try it and see. I did on the 55 days, and all that happened is I got a
different error, but maybe things are different under 60 with the right PP.
Apparently, it is not merely the need for BA that keeps this from working,
and the "real" problem may be why HP did not ship ps.hpbin.sys with BA.

While this is almost certainly in the archives several times (along with
discussion of why to kill these daemons under the user name of their jobs
and other considerations), here is the necessary logic for nmbd, although it
can be adapted for other daemons (another exercise for the reader?). These
lines work fine from the command line, and will not work in a job stream
(and yes, I am including or excluding the ! and other job artifacts as
appropriate).

XEQ PS.HPBIN.SYS '-A -U MGR.SAMBA'>PSLIST
XEQ GREP.HPBIN.SYS NMBD.SAMBA.SYS<PSLIST>NMBLIST
INPUT STRING<NMBLIST
XEQ SH.HPBIN.SYS "-c 'kill ![WORD(STRING)]'"

Or, if you don't want to actually kill the NBMD and end the job, then
ECHO ![WORD(STRING)]

In any case, we used to be out at first base, when trying this from a job
stream. ps would not work. I doubt that it does in any case except where
one's system has the eponymous patch given as the subject. This should at
least be a comfort for those of us using third party job management products
which complain when a job is aborted. kill gives us a graceful exit, with no
error messages to cause alarm.

Greg Stigers
http://www.cgiusa.com

-----Original Message-----
From: Barry Lake [mailto:[log in to unmask]]
Sent: Tuesday, December 05, 2000 2:55 PM
To: [log in to unmask]
Subject: Re: PX2LXD4(A)

Why can't you just do

  LinkEd> altprog kill.hpbin.sys;cap=ba,ia,ph

and add BA yourself?

HP may have made the error in not sending you a version of KILL that has
BA, but there's no reason why you can't add it after the fact. (BTW, my
version of KILL on 6.0 PP2 already had BA when I checked, but someone else
here might have added it)

Barry Lake                              [log in to unmask]
Allegro Consultants, Inc.               www.bogus.allegro.com
(408)252-2330
--------
Attempting to reduce spam influx.
Remove ".bogus" to create valid address.

ATOM RSS1 RSS2