Resolving process does not send messages to the screen. It writes its messages to the file rvnamed-ng.log in the IPTraf-ng log directory.
Unable to open child communication socket
Resolving process was unable to open the communication endpoint for data reception from the children it creates. This is highly unusual and should it occur, report the circumstances.
Unable to open client communication socket
Resolving process was unable to open the communication endpoint for data exchange with the IPTraf-ng program. This is highly unusual and should it occur, report the circumstances.
Error binding client communication socket Error binding child communication socket
Resolving process was unable to assign a name to the indicated communication socket. This may be due to a bad, full or corrupted filesystem.
Fatal error: no memory for descriptor monitoring
Resolving process ran out of memory. IPTraf-ng will resort to blocking and may freeze.
Error on fork, returning IP address
Resolving process had a problem spawning a copy of itself to resolve the IP address; it will simply return the IP address in its literal, dotted-decimal notation. IPTraf-ng will still function normally. This may be due to lack of memory or a process limit hit.
Maximum child process limit reached
Resolving process has reached its maximum number of child processes. This is intended as a "brake" to prevent too many children from hogging your computer's resources and possibly crashing it. Unless IPTraf-ng is monitoring an extremely busy network without filters, this shouldn't happen, at least, not that often. If you notice this message, try applying filters or check your DNS server. Many times, this can happen when the DNS server goes down for whatever reason and you have resolving process children taking too long to resolve.