[27597] in Athena Bugs
Re: debathena-zephyr-config if-up being run too early
daemon@ATHENA.MIT.EDU (Edward Z. Yang)
Mon Sep 3 14:09:14 2012
Content-Type: text/plain; charset=UTF-8
From: "Edward Z. Yang" <ezyang@mit.edu>
In-reply-to: <BD9B9ACE-2A52-4860-9DB0-9CE1086176C9@mit.edu>
To: debathena <debathena@mit.edu>
Date: Mon, 03 Sep 2012 14:08:51 -0400
Message-Id: <1346695573-sup-297@javelin>
Content-Transfer-Encoding: 8bit
Cc: bugs <bugs@mit.edu>, kcr@mit.edu
Errors-To: bugs-bounces@mit.edu
Excerpts from Jonathan Reed's message of Mon Sep 03 14:05:52 -0400 2012:
> What Ubuntu version does this occur on?
Ubuntu Precise 12.04.1
> And what hardware?
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
> If ifup.d is actually running before an interface is up, that's arguably an upstream bug.
I agree.
> But I've also seen poor interactions with some chipsets (primarily Broadcom) where the interface is brought up, but nothing is actually useful because the chipset takes a few seconds to test for a physical link and do other stupid stuff. And if this is wireless, all bets are off.
Yes, this is wireless.
> Arguably, this is related to http://debathena.mit.edu/trac/ticket/133 And I think is firmly in the "patches welcome" state. I don't have a good answer here, though I'm intrigued by your assertion that zhm doesn't need to care about when it is moved across networks.
I think Karl would have more to say here:
unsipb / zhm / kcr 23:33 (No, I don't have a Solaris box! Nor do I have an Apple 2 or a fax machine!)
I'm also sort of unconvinced that as long as you start it
the first time with network and working dns, that you should need to
restart it on network change.
Going through and reading the code to become more or less convinced is
something I need to make a note to do.
Cheers,
Edward
