public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out
Date: Fri, 29 Aug 2003 10:25:48 +0200	[thread overview]
Message-ID: <yw1x1xv498fn.fsf@users.sourceforge.net> (raw)
In-Reply-To: 3F4EB641.3040107@davehollis.com

David T Hollis <dhollis@davehollis.com> writes:

>>Thank you, thank you, thank you. I was just thinking today how
>>annoying it is that whenever I boot up my laptop, dhclient runs and tries
>>to get an IP address on the ethernet interface until it's ^C'd. Since
>>I often use the Ethernet interface this is not a bad default, but dhclient
>>can't even realize on its own that there's no cable plugged in.
> 
> Hmm, that seems to raise the question - why doesn't dhclient just
> handle that?  On a DHCP interface, it's running anyway.  if it paid
> attention to link status, it would know when to re-request an IP.  If
> you are statically assigned, you don't really care anyway.

Well, sometimes it's better to not have the interface configured UP
when there's no cable connected.  It avoids some very long timeouts
when some program tries to connect to something.  It's better to just
get a host unreachable error immediately.

-- 
Måns Rullgård
mru@users.sf.net


  reply	other threads:[~2003-08-29  8:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 21:21 [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out Bryan O'Sullivan
2003-08-28 21:35 ` Jeff Garzik
2003-08-28 21:46 ` Christoph Hellwig
2003-08-28 21:50   ` Bryan O'Sullivan
2003-08-28 21:54 ` J.A. Magallon
2003-08-28 22:34   ` Jeff Garzik
2003-08-28 22:45     ` J.A. Magallon
2003-08-28 22:49       ` Bryan O'Sullivan
2003-09-03  8:42       ` Stefan Rompf
2003-08-29  0:34 ` Aaron Lehmann
2003-08-29  2:11   ` David T Hollis
2003-08-29  8:25     ` Måns Rullgård [this message]
2003-08-29 17:43     ` Bryan O'Sullivan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yw1x1xv498fn.fsf@users.sourceforge.net \
    --to=mru@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox