Subject: Re: talk (old and new)
To: None <>
From: Wolfgang Solfrank <>
List: netbsd-bugs
Date: 01/25/1994 14:53:56
Note that there is a bug in talk. It doesn't agree with the kernel on the
action to be done on an interrupted connect system call.

I.e., the program sets up an one second timer to update the message on top
of the screen. This timer might interrupt the connect call when it waits
for the tcp connection to be established. The interrupted connect returns
with EINTR and talk tries to restart it within a loop. But the second call
to connect returns with an EADDRINUSE.

I'm not sure who is at fault here. Should the connect call simply continue
(would be more like what an innocent user would expect), or should it be
the responsibility of the application to handle this condition?
ws@TooLs.DE     (Wolfgang Solfrank, TooLs GmbH) +49-228-985800