Application programs registering and using cross-machine services make use of the netname interface to MachNetIPC. The ``nns'' interface to MachNetIPC can operate either as the sole name server on a node, or in cooperation with a service that is already running (such as ``snames'' or ``netmsgserver''), although this latter configuration slightly complicates the initial contact with the service. See the appendix section about ``nns'' for more information on how to use this service. The host administrator should decide whether to run MachNetIPC alone or in cooperation with other services.
The MachNetIPC service can be added to the boot time server startup script nanny.config in place of the ``netmsgserver''. Consult your local system administration guide for more information about server startup procedures. Note that the x-kernel must be started with a user id that has permission to access the master device port. If your site does not have a RARP server (an unusual circumstance), you may find it necessary to create a ROM file and start the xkernel image file from the directory with the rom file. See section 13.2 and the ARP man page in appendix A for details.
If the x-kernel terminates or is terminated, it can be restarted easily (``xkernel &'').