Hello,
My Qnx blocked during a commissioning. I was installing new programs with a
modem connection and sudentlly, after typing “sin” I lost communication and
the costumer said that the machine was complitelly blocked (he wasn’t happy
at all…).
Does anyone had the same problem?
I could reproduce the problem in a local machine also typing sin locally but
I don’t really know where the problem is. Last thing I changed in the system
was to add some USB drivers for a printer…
I’m thinking to add a “chmod a-x /bin/sin” in my rc.local because I work
very often with Qnx4 and sometimes I don’ t remember pidin exists…
Thanks
David Porta <DavidPorta@nospam.es> wrote:
Hello,
My Qnx blocked during a commissioning. I was installing new programs with a
modem connection and sudentlly, after typing “sin” I lost communication and
the costumer said that the machine was complitelly blocked (he wasn’t happy
at all…).
Does anyone had the same problem?
I could reproduce the problem in a local machine also typing sin locally but
I don’t really know where the problem is. Last thing I changed in the system
was to add some USB drivers for a printer…
I’m thinking to add a “chmod a-x /bin/sin” in my rc.local because I work
very often with Qnx4 and sometimes I don’ t remember pidin exists…
Thanks
It could be PR 21549. Fixed in patch 234:
http://www.qnx.com/download/feature.html?programid=13008
-seanb
I have seen a problem like this with QNX 4. It occured when using
the command “sin ver”. This command causes a message to
be sent to all resource managers that have turned on a bit indicating
they support the command. If the implimentation by this resource
manager is wrong, all sorts of bad things can happen. The least is
that sin does not return. The worst is that a hard loop occurs in
the resource manager. To diagnose this, start a shell at a high
priority and after the “sin ver” run a regular sin to see
what resource manager is causing the problem. Then if you can, fix
it.
Thanks I will test both
David
“maschoen” <maschoen@pobox-dot-com.no-spam.invalid> escribió en el mensaje
news:eqtc9h$dk5$1@inn.qnx.com…
I have seen a problem like this with QNX 4. It occured when using
the command “sin ver”. This command causes a message to
be sent to all resource managers that have turned on a bit indicating
they support the command. If the implimentation by this resource
manager is wrong, all sorts of bad things can happen. The least is
that sin does not return. The worst is that a hard loop occurs in
the resource manager. To diagnose this, start a shell at a high
priority and after the “sin ver” run a regular sin to see
what resource manager is causing the problem. Then if you can, fix
it.