minor bug in nsd-xfer

Fri Feb 4 07:59:34 UTC 2005

On Thu, Feb 03, 2005 at 10:19:14PM +0000,
 Nick Hilliard <nick-lists at netability.ie> wrote 
 a message of 14 lines which said:

> nsd-xfer appears to be spinning somewhere and chewing up CPU, which
> is bad stuff.

It *seems* (warning: this thinking comes only from a static
observation of the code) that read_socket() loops forever when read(2)
returns zero (for instance if the TCP conenction was shut down).

If so, my patch address this issue.

As you said, gdb will prove or disprove my theory. strace or truss or
a similar tool may also show calls to read(2) which returns zero.