From owner-freebsd-net@FreeBSD.ORG Sat Feb 22 17:10:01 2014 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A7B9F958 for ; Sat, 22 Feb 2014 17:10:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (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 7790B18D2 for ; Sat, 22 Feb 2014 17:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1MHA1ej079943 for ; Sat, 22 Feb 2014 17:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1MHA1l2079942; Sat, 22 Feb 2014 17:10:01 GMT (envelope-from gnats) Date: Sat, 22 Feb 2014 17:10:01 GMT Message-Id: <201402221710.s1MHA1l2079942@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: "J.R. Oldroyd" Subject: Re: conf/183407: [rc.d] [patch] Routing restart returns non-zero exitcode in case of no extra routing parameter or missing atm/ipx X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: "J.R. Oldroyd" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Feb 2014 17:10:01 -0000 The following reply was made to PR conf/183407; it has been noted by GNATS. From: "J.R. Oldroyd" To: bug-followup@FreeBSD.org, abhikumar163@gmail.com Cc: Subject: Re: conf/183407: [rc.d] [patch] Routing restart returns non-zero exitcode in case of no extra routing parameter or missing atm/ipx Date: Sat, 22 Feb 2014 12:07:10 -0500 I've received bug reports for wifimgr(8) when it resets interfaces using "/etc/rc.d/netif restart ifname" which calls /etc/rc.d/routing which is returning an incorrect value of 1. The patch proposed here does indeed fix things.