: Hi All,
: How could a process act this way? We are using many shared and static
: libraries, could this have something to do with it? We are also using a
: messaging middleware (DEC MessageQ) that polls on a communications port -
: another possibility? I am not familiar with the internals of UNIX, but there
: must be a way to kill the process and/or discover the source of this unusual
: I am on version HPUX 10 and building the executables using the CC compiler.
I'm not too sure about HPUX, but I have had problems under both Solaris 2x,
Solaris 1x, and AIX, where the process is accessing a SCSI device,
w/o disconnect, and I kill the process, and it will not die, because the
process is already blocked. Or more accurately, it won't die until the
SCSI command finishes. [Which can take up to a half-hour...]
The same thing may be occuring w/ the com port thingy if the process
interacts with it.
COMMERCIAL SOLICITATIONS ARE NOT WELCOME AT THE ABOVE ADDRESS.