Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Feb 2006 19:29:30 +0000 (UTC)
From:      Maxime Henrion <mux@FreeBSD.org>
To:        projects-committers@FreeBSD.org, cvs-projects@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   cvs commit: projects/csup proto.c
Message-ID:  <200602021929.k12JTUiB010470@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
mux         2006-02-02 19:29:30 UTC

  FreeBSD projects repository

  Modified files:
    csup                 proto.c 
  Log:
  Revert most of my previous changes, I'm actually going to handle this
  another way.  When looping through all the available addresses returned
  by getaddrinfo(), if either the socket() or the connect() call fails,
  print a "Cannot connect to" message, but print the address and not the
  host, with inet_ntop().  On ref4.FreeBSD.org which doesn't support IPv6
  and using cvsup5.FreeBSD.org which expands to both an IPv4 and an IPv6
  address this gives:
  
  Connecting to cvsup5.FreeBSD.org
  Cannot connect to 1c1c:176f::2001:468:902:201: Protocol not supported
  Connected to cvsup5.FreeBSD.org
  [...]
  
  Now the only problem is that it would seem more logical to also print
  the address in the "Connected to" line, so that we have:
  
  Connecting to cvsup5.FreeBSD.org
  Cannot connect to 1c1c:176f::2001:468:902:201: Protocol not supported
  Connected to 128.205.32.21
  
  But I'm reluctant to do this since that changes the makes us differ
  significantly from CVSup's output.
  
  Revision  Changes    Path
  1.58      +28 -24    projects/csup/proto.c



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602021929.k12JTUiB010470>