Traditional message queue manager (QNX Neutrino)

Note: You must be root to start this manager.


mqueue [-d] [-p priority] &

Runs on:



Don't daemonize.
-p priority
Run at the given static priority.


The mqueue manager implements traditional POSIX 1003.1b message queues. When you create a queue, it appears in the pathname space under /dev/mqueue.

Note: The /dev/mqueue directory doesn't appear until you actually create a queue.

The traditional POSIX message queue manager is a resource manager that uses messages to communicate with its clients. You can access it locally or remotely, allowing for network-wide message queues. On a self-hosted Neutrino system, the default sysinit script starts mqueue; for more information, see the Controlling How Neutrino Starts chapter of the Neutrino User's Guide.

  • You can have only one of the alternate message queue manager (mq) and mqueue running on your system at any time.
  • Starting with release 6.3.0, procnto manages named semaphores, which mqueue used to do (mqueue still manages named semaphores if it detects that procnto isn't doing so).

For more information, see the POSIX Message Queues: Two Implementations technote.

See also:

mq, procnto*

mq_close(), mq_getattr(), mq_notify(), mq_open(), mq_receive(), mq_send(), mq_setattr(), mq_unlink() in the QNX Neutrino C Library Reference

POSIX message queues in the “Interprocess Communication (IPC)” chapter of System Architecture

Controlling How Neutrino Starts in the QNX Neutrino User's Guide

POSIX Message Queues: Two Implementations technote