From owner-freebsd-rc@FreeBSD.ORG Fri Nov 18 20:45:55 2011 Return-Path: Delivered-To: freebsd-rc@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E183106566C; Fri, 18 Nov 2011 20:45:55 +0000 (UTC) (envelope-from rea@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 0C9B68FC16; Fri, 18 Nov 2011 20:45:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=codelabs.ru; s=two; h=Sender:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=R4lXr+Ai6QoVMg8VzEba477Kg3NoeaLGvSptmoTTkcQ=; b=HXLQBeeVsnq7IVEUqDuBEduQIoq6DwP75u3qc258RWWo9kLg4eGIJKPsAsXasYQ4vr0CTzUUN1Bz0XCvCqetBJGm4FJzUHGAezQmYiCAkqh2JmikZrzwTGYwwN/hZ6kRoLakVVjRPasg4zu7tecz6o19M9ezQlvgHLYTIcxynaRUIHgg+HJOTzVmpxWE0EeQSzTb9cfStm1gYxz7DqDFuDbUyuXU2a4JOgK2Z1m7bjDz7S5+kwDl+jy15mugtWyXU3G7m3OLheBxgRvJmFbf9mEXHD48tixYug4SYdKzIWen9Zc5osHTHpe8YgaeeF3o5FdzXqiyHySp9ERr0RtuMw==; Received: from shadow.codelabs.ru (ppp91-77-172-150.pppoe.mtu-net.ru [91.77.172.150]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1RRVJp-000IIR-UZ; Fri, 18 Nov 2011 23:45:54 +0300 Date: Sat, 19 Nov 2011 00:45:52 +0400 From: Eygene Ryabinkin To: d@delphij.net Message-ID: References: <4EB6693F.2020102@delphij.net> <4EB71580.20507@FreeBSD.org> <4EB72290.8030104@delphij.net> <4EC6C247.6040807@delphij.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bCsyhTFzCvuiizWE" Content-Disposition: inline In-Reply-To: <4EC6C247.6040807@delphij.net> Sender: rea@codelabs.ru Cc: Doug Barton , freebsd-rc@FreeBSD.ORG Subject: Re: Annoying ERROR: 'wlan0' is not a DHCP-enabled interface X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2011 20:45:55 -0000 --bCsyhTFzCvuiizWE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Xin, good day. Fri, Nov 18, 2011 at 12:38:31PM -0800, Xin LI wrote: > Is there any counter reasoning about "having an interface marked as > non-DHCP is not an error"? I'm still not convinced with the benefit > of having it show an error message. Well, when I invoke 'service dhclient start em0' and em0 isn't DHCP-enabled, I want to see some diagnostics on why I was not able to get DHCP on that interface. Return code isn't that visible (I can, of course, always run it as 'service dhclient start em0 || echo failed'), but I am not up to typing more than needed and I should see the real reason for absence of DHCP-assigned address in that case, be it the non-DHCP-enabled interface or some other problem. --=20 Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] --bCsyhTFzCvuiizWE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iF4EAREIAAYFAk7GxAAACgkQFq+eroFS7PuR8gEAi8B0qQYGbiv0OqmDILlfGYjm XZ1AwfyCEpi/Eu0beLUA/2QmrNjXT2UgZEY+l6NEHI2LwJfjuUV2YIWpCqIawgWm =Y0mk -----END PGP SIGNATURE----- --bCsyhTFzCvuiizWE--