From owner-freebsd-current@FreeBSD.ORG  Wed Oct  2 10:28:32 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 40AC9348
 for <freebsd-current@freebsd.org>; Wed,  2 Oct 2013 10:28:32 +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 D6459289C
 for <freebsd-current@freebsd.org>; Wed,  2 Oct 2013 10:28:31 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.80.1 (FreeBSD))
 (envelope-from <lists@c0mplx.org>) id 1VRJfF-0005Ap-VR
 for freebsd-current@freebsd.org; Wed, 02 Oct 2013 12:28:17 +0200
Date: Wed, 2 Oct 2013 12:28:17 +0200
From: Kurt Jaeger <lists@c0mplx.org>
To: freebsd-current@freebsd.org
Subject: PR 181532: src/sbin/route/route.c patch for a more useful error
 message
Message-ID: <20131002102817.GK2951@home.opsec.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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: Wed, 02 Oct 2013 10:28:32 -0000

Hi!

In the thread 

http://lists.freebsd.org/pipermail/freebsd-current/2013-August/043926.html

someone stumbled upon a not very helpful error message from:

# route get

The error message is strange/misleading:

route: writing to routing socket: Invalid argument

The patch in

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

changes this to:

route get requires a parameter, try 'default'

Can someone commit this change ?

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