Network console daemon servers exist for both Wanda and Unix. The Wanda one is preferred, and is normally used in conjunction with xscons which presents the console output of the various ports in separate widgets.
A Unix Network Console Daemon was written to allow redirecting of the output of the network console output to a Unix process that has a MSNL listening process at one end and does TCP listening at the other end. Thus xwcons will be able to connect directly to the daemon (setup the machine.Console entry in the trader to be doing TCP connection).
The netcond daemon reads a configuration file to determine which Wanda network console client to serve. The format of the configuration file assume each line to indicate a machine in which this server is serving. The daemon will then check with trader to confirm that this information is indeed correct and obtains the port number for the TCP listen.
When a netcon client connects to the netcon server, it will register this entry with the netcon server and try to do a join of this netcon client and an existing xwcons TCP connection.
Correspondingly, when a TCP listened socket returns from select, we do an accept, register this new entries and try to join this with the corresponding netcon client.
Whenever any end of a join is broken, we destroy the join and free the registration associate with the socket.
The usage of the corresponding Unix tool is:
netcond [-d] [-l log_file] [-c config_file]
where -d specifies the debug mode, -p specified the alternative MSNL port other than the MSNLPORT_NETCON defined, -l specifies alternative log file location (default /tmp/netcond.log) and -c specifies configuration file location (default to look at /etc/netcon.conf follow by ./netcon.conf).
Remember that the MSNL connection between the Wanda machine and the Unix daemon will be unreliable.