Date: Sat, 19 Nov 2011 00:45:52 +0400 From: Eygene Ryabinkin <rea@FreeBSD.ORG> To: d@delphij.net Cc: Doug Barton <dougb@FreeBSD.org>, freebsd-rc@FreeBSD.ORG Subject: Re: Annoying ERROR: 'wlan0' is not a DHCP-enabled interface Message-ID: <VMhPQj/s0331SNZXLVpdbaNAyBY@RzV33t0qf/tQbqPDH2EX0VmGCGw> In-Reply-To: <4EC6C247.6040807@delphij.net> References: <4EB6693F.2020102@delphij.net> <4EB71580.20507@FreeBSD.org> <4EB72290.8030104@delphij.net> <Snqh5lmyPm2YvkGpN1vSomauXwU@g5jH1yj%2BTnAiSdLOy3xs5Jutvhc> <4EC6C247.6040807@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?VMhPQj/s0331SNZXLVpdbaNAyBY>