From owner-freebsd-current@FreeBSD.ORG  Tue Aug 27 13:21:48 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 98A268E7;
 Tue, 27 Aug 2013 13:21:48 +0000 (UTC)
 (envelope-from lists@c0mplx.org)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5A2FD2719;
 Tue, 27 Aug 2013 13:21:48 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.80.1 (FreeBSD))
 (envelope-from <lists@c0mplx.org>)
 id 1VEJDN-0002XR-Cy; Tue, 27 Aug 2013 15:21:45 +0200
Date: Tue, 27 Aug 2013 15:21:45 +0200
From: Kurt Jaeger <lists@c0mplx.org>
To: Pawel Pekala <pawel@FreeBSD.org>
Subject: Re: route get fails
Message-ID: <20130827132145.GX2951@home.opsec.eu>
References: <20130824134223.6bf7634c@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130824134223.6bf7634c@FreeBSD.org>
Cc: freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 13:21:48 -0000

Hi!

> For some time now I get this:
> 
> [corn:~]> route get
> route: writing to routing socket: Invalid argument
> 
> Is this just my build or anyone can confirm this?

A patch for route to display a more useful error message:

  http://www.freebsd.org/cgi/query-pr.cgi?pr=181532

-- 
pi@opsec.eu            +49 171 3101372                         7 years to go !