Donna Garverick wrote:
>
> Mark Bixby wrote:
>
> > The trick required here is you need to use the -c option to see the shell
> > you're executing a single command, i.e.:
> >
> >         :XEQ SH.HPBIN.SYS "-c 'kill `cat logs/httpd.pid`'"
>
> sooo...as long as we're on the subject....
>
> *why* do we want to kill things like apache (and sendmail, syslog, samba) instead
> of abortjobbing (new word :-) them?

What "kill" actually does is to send a signal to a process.  The process can
register signal handlers that will be executed when a signal arrives, or if no
handlers are registered, the OS will perform certain default actions
automatically.

Any POSIX-based app whose documentation requests that you use "kill" to shut it
down most likely has registered signal handlers that will perform a clean
shutdown after the signal is receive and then terminate politely after flushing
application buffers to disk, gracefully terminating TCP connections, removing
semaphores, etc, etc.

:ABORTJOB is of course brutal and won't do any of those cleanup things.

> i know mark's presentation said something
> about leaking semaphores but i don't see any puddles under my computer :-)

The ballast in those 2-meter cabinets includes a drip pan for catching
semaphore leaks.  ;-)

> (and just what is 'ipcs' telling me???)               - d

IPCS reports on the individual SVIPC shared memory, semaphore, and message
queue objects that current exist on your machine.

For more info about IPCS and SVIPC, see:

http://docs.hp.com/cgi-bin/doc3k/B3643090008.12947/1
or
http://docs.hp.com:80/dynaweb/smpe/b1019/b957/@Generic__BookView

- Mark B.