I have found that psin fails in lots of scenarios. Mainly when I want to
scroll down the viewable list of processes, and when I least expect it.
Pity really as it’s quite an informative utility.
I haven’t been inclined to mention it here before as I’m being quite
brutal with my machines in the area of interrupts and the odd timer or
three, and it could be argued that I am provoking it.
I’m learning to live without it (psin) but I find pidin and sin lacking
in some of the information I am after about what’s going on in the
Robert Rutherford wrote:
We have reported a similar problem and so have a few others. Do you also
find that “psin” fails in this scenario?
So far the silence from QSSL has been deafening.
“Joaquin Ferruz Melero” <> email@example.com> > wrote in message
news:> 3DF5E94B.firstname.lastname@example.org> …
I attach a small program which does something simple: First it
programs a posix timer; the timer will send the process a SIGKILL signal
when it expires, so that the process should die. Then it loops without
end. It has also a handler for SIGUSR1 which will print the remaining
count for the timer if such signal is sent to the process.
Well, as a matter of fact, the process won’t die! If you kill it
BEFORE the timer has expired, it disappears, as expected. However, if
you wait for the timer to send the process SIGKILL, you find that a)
This does not kill the process b) You CANNOT kill the process, even with
SIGKILL. c) If you type ps -l -p , “ps” will loop forever
while it prints the stuff for the non-dead process over and over…
It happens under QNX 6.2, and QNX 6.1; it does not happen under
Solaris 2.6. The process dies, however, if the timer sends SIGTERM, and
its handler calls exit(0).
Is this a system bug?
Realtime Technology Systems Pty Ltd
2 Hadleigh Circuit
Phone: 61-2-6291 3833
Fax: 61-2-6291 3838
Mobile: 0413 634 667