We have a system that has multiple tasks, each of which has stdout and
stderr set to a particular console device. Normally the output of these
tasks can only be viewed by switching (ctrl-alt-2, e.g.) to the console used
by the task. The exception seems to be /dev/con1. When the task attached to
that console writes to it, the currently displayed console switches to
/dev/con1, with no operator intervention. This can be annoying.
Is there any particular reason that this is happening? Is there any way to
prevent it?
Thanks,
Kevin
kevin.miller@transcore.com
Kevin Miller <kevin.miller@transcore.com> wrote:
We have a system that has multiple tasks, each of which has stdout and
stderr set to a particular console device. Normally the output of these
tasks can only be viewed by switching (ctrl-alt-2, e.g.) to the console used
by the task. The exception seems to be /dev/con1. When the task attached to
that console writes to it, the currently displayed console switches to
/dev/con1, with no operator intervention. This can be annoying.
Is there any particular reason that this is happening? Is there any way to
prevent it?
This shouldn’t be happening – console switches should not happen on
output, and /dev/con1 should have nothing special about it.
Is it possible that the routine writing to /dev/con1 is using the
console_active() function to make its console active after doing the
output?
-David
QNX Training Services
I do not answer technical questions by email.