Provide service support to remote IDE components


qconn [-alv] [bind=bind_address] [child_prio=cpriority]
      [port=portnum] [qconn_prio=qpriority]

Runs on:

QNX Neutrino


(QNX Neutrino 6.6 or later) Don't disable address space layout randomization (ASLR). The default is to disable it.
(QNX Neutrino 6.6 or later) Accept connections only from the local host (to use with ssh tunneling).
Display the version number for qconn, and then exit.
(QNX Neutrino 6.6 or later) Accept connections only from this IP address.
Set the priority at which children are run. The default is 10.
Select a different port to bind the daemon to. The default is 8000. If you aren't logged in as root when you start qconn, it can't bind to a restricted port number.
Set the priority at which qconn runs. The default is 10.

Use this option to increase qconn's priority if CPU-intensive programs are running at the same or a higher priority, preventing qconn's clients from receiving data. For example, getting a "Could not find target: Read timed out." error while running the IDE's System Profiler means that the System Profiler is unable to receive data from qconn on the target.


The qconn daemon is a service provider that provides support, such as profiling system information, to remote IDE components. Output is based on the services invoked and is fed to the requesting IDE component on a remote host.

Note: If you aren't logged in as root when you start qconn, it can't start resource manager components.

The functionality comes from the service modules that are currently bound directly into the executable.

Note: Currently, if you want to use the debugger, you must have pdebug installed on your system in the search path used when qconn is launched. You may also have pdebug in /usr/bin.


Other supporting files are required, depending on the service being used. For example, the memory analysis service requires that librcheck.so be installed in the user's path.


The qconn daemon lets anyone run any application on your target system as the superuser. Obviously, this is a huge security risk. Don't include qconn on systems being deployed to customer sites.