qconn

Provide service support to remote IDE components

Syntax:

qconn [port=portnum]
      [qconn_prio=qpriority]
      [child_prio=cpriority]

Runs on:

Neutrino

Options:

port=portnum

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.

qconn_prio=qpriority

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 QNX Momentics IDE's System Profiler means that the System Profiler is unable to receive data from qconn on the target.

child_prio=cpriority

Set the priority at which children are run. The default is 10.

Description:

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.

---

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.

---

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.

---

Files:

Supporting files are required, depending on the service being used. For example, the memory analysis service requires libmalloc.so installed in the user's path.

Caveats:

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.

See also:

IDE User's Guide