From owner-freebsd-current  Sun Aug  6 13:16:38 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id NAA03222
          for current-outgoing; Sun, 6 Aug 1995 13:16:38 -0700
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id NAA03211
          for <freebsd-current@FreeBSD.org>; Sun, 6 Aug 1995 13:16:35 -0700
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id NAA18456; Sun, 6 Aug 1995 13:16:29 -0700
To: freebsd-current@FreeBSD.org (FreeBSD-current users),
        joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
Subject: Re: workaround for talk's address problem 
In-reply-to: Your message of "Sun, 06 Aug 1995 18:03:27 +0200."
             <199508061603.SAA07779@uriah.heep.sax.de> 
Date: Sun, 06 Aug 1995 13:16:29 -0700
Message-ID: <18450.807740189@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: current-owner@FreeBSD.org
Precedence: bulk

> talk(1) has problems with multi-homed hosts.  To negotiate the
> connection with the remote peer, it uses the first address as returned
> by a call to gethostbyname().  This will cause the connection to hang

NFS has the exact same problem, FWIW.  If there's a more general
solution, we should go for it.

						Jordan