Unable to kill kernel thread

Anyone ever seen that message before?
Anyone knows what’s causing it?

It’s been quite a while since I’ve worked on QNX4. But isn’t that what you
get when a process isn’t replying to a system death message?


“Francis Greyss” <fgreyss@icstriplex.ca> wrote in message
news:dtcokc$jqo$1@inn.qnx.com

Anyone ever seen that message before?
Anyone knows what’s causing it?

Thanks for your answer Bill but don’t you think that when a process is
killed, it receives a signal, not a message to which it must reply?


“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:dtdgp5$5h1$1@inn.qnx.com

It’s been quite a while since I’ve worked on QNX4. But isn’t that what
you get when a process isn’t replying to a system death message?


“Francis Greyss” <> fgreyss@icstriplex.ca> > wrote in message
news:dtcokc$jqo$> 1@inn.qnx.com> …
Anyone ever seen that message before?
Anyone knows what’s causing it?
\

You are correct, it receives a signal. But then, any server processes which
wish to can register with Proc and receive a death message. The death
message contains certain information about the process that just died. The
server can use this information to release any resources that that process
may have been using, etc. However, . . .

since it is a message, it must be replied to. It doesn’t matter what the
reply is, it will be ignored. When proc receives the reply it then messages
the next process that is registered to receive these death messages. I
believe that there is a 30 second time-out on the reply. If that time-out
is reached that’s when you see the message you are seeing.

I think.


“Francis Greyss” <fgreyss@icstriplex.ca> wrote in message
news:dtnq6p$bpk$1@inn.qnx.com

Thanks for your answer Bill but don’t you think that when a process is
killed, it receives a signal, not a message to which it must reply?


“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:dtdgp5$5h1$> 1@inn.qnx.com> …
It’s been quite a while since I’ve worked on QNX4. But isn’t that what
you get when a process isn’t replying to a system death message?


“Francis Greyss” <> fgreyss@icstriplex.ca> > wrote in message
news:dtcokc$jqo$> 1@inn.qnx.com> …
Anyone ever seen that message before?
Anyone knows what’s causing it?


\