NetWare 4.1/9000 Concepts

1-116
NetWare Glossary
N
The primary function of NEMUX is to schedule work for NetWare Services
engines as messages arrive upstream and to route messages to the
appropriate downstream protocol stack.
NEMUX passes messages between the NetWare Services processes and the
NetWare protocol stack in NetWare core protocol (NCP).
NEMUX interacts with four types of NetWare Services processes—the
NetWare daemon, engine processes, ancillary processes, and admin
processes. All run as root users.
• NetWare daemon. Builds the stream that links NEMUX to the protocol stacks
and starts the engine and ancillary processes.
• Engine processes. Daemons responsible for many of the NetWare Services
functions. Clients typically interact with NetWare Services engine processes in a
request-response scenario through NEMUX. Messages are received by NEMUX
and passed to an engine which sends a response message to the NEMUX client
NEMUX is not aware of the request response mechanism, but it does send
information to the underlying protocol to allow it to properly manage the
message context. NEMUX knows, however, when an engine has completed its
work so that new work can be scheduled to that engine.
• Ancillary processes. Typically process work that would cause an engine process
to block for an unknown period of time, or they perform background processing.
They do not receive network messages but can receive messages through IPC
(interprocess communications) from engines or other processes. Some ancillary
processes can send messages to any client.
• Admin processes. Similar to ancillary processes but are not started by the
NetWare daemon. They perform administrative functions that view or alter the
state of NEMUX and NetWare Services processes.
NetWare inode
A file—USInode—that stores all NetWare and name space information
about data files in a NetWare volume on a HP-UX system. This information
is specific to NetWare files and is not kept by the HP-UX operating system.