Re: Ctrl-c abort of dhclient during rc.d start aborts all network configuration

From: Brooks Davis (brooks_at_one-eyed-alien.net)
Date: 08/31/05

  • Next message: Jilles Tjoelker: "Re: [PATCH] caching daemon release and nsswitch patches" 
    Date: Wed, 31 Aug 2005 12:46:12 -0700
To: Robert Watson <rwatson@freebsd.org>

    On Wed, Aug 31, 2005 at 12:10:44PM +0100, Robert Watson wrote:
    >
    > I believe this is related to the new dhclient -- when I run my notebook
    > disconnected from the network, the boot pauses for about 15-20 seconds
    > waiting for a link on xl0. Being impatient when booting in airports just
    > before my flight, I like to hit Ctrl-C and abort it, since I know that
    > there will be no link. In the old world order, this was fine, dhclient
    > was simply killed and all was good. In the new world order, it kills all
    > of the netif startup script, and for some reason (ordering related,
    > presumably), this prevents 127.0.0.1 from being configured on lo0, which
    > causes a number of applications to die, since 0.0.0.0 cannot be bound. It
    > sounds like a couple of things are unfortunate here:

    The wait should be 10 seconds plus some startup time.

    > (1) It would be good to configure lo0 first.

    Interfaces are configured in order of index by default. If lo0 were
    attached sooner, it would be configured sooner. I'm somewhat tempted to
    change it from it's current (apparently bogus) position in the startup
    process at SI_SUB_PROTO_IFATTACHDOMAIN to SI_SUB_INIT_IF/SI_ORDER_ANY
    and push the l2com attachments from SI_ORDER_ANY to SI_ORDER_MIDDLE.
    Strictly speaking I think lo(4) should be SI_SUB_PSEUDO, but moving it
    up so it attached first makes some sense given how critical it is.

    Alternativly, one could add code to sort the result of "ifconfig -l" to
    configure lo0 first.

    > (2) If a dhclient is ctrl-c'd, it would be nice if the rest of the network
    > configuration continued.

    I don't see any code in the startup scripts that would cause them to
    exit on failure so the issue is probalby that the signal is being
    delivered to the /etc/rc.d/netif instance. I don't really know what the
    solution to that is.

    > The printing of '.'s in dhclient is also a bit excessive.

    Hanging with no output seems even less unhelpful. :( Longer term I want
    to get rid of syncronous calls to dhclient in the startup process, but I
    haven't had time to work on it and IMO, it's a bit late in the game for
    6.0.

    -- Brooks
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Jilles Tjoelker: "Re: [PATCH] caching daemon release and nsswitch patches"

    Relevant Pages

    • Re: Starp up sequence
      ... >> RunServicesOnce ... >> User Profile Startup Folder ... >> the programs specified in the Computer Configuration setting just before ... >> AppInit_DLLs Registry value. ...
      (microsoft.public.windowsxp.customize)
    • RE: programs in tray
      ... Microsoft Windows XP by using the System Configuration utility ... Programs that are set to load during the startup process (these programs ... permanently deletes all restore points for the System Restore utility. ...
      (microsoft.public.windowsxp.customize)
    • Re: Ctrl-c abort of dhclient during rc.d start aborts all network configuration
      ... > change it from it's current position in the startup ... > configure lo0 first. ... out not to be very practical using our default boot scripts (since many ... >> configuration continued. ...
      (freebsd-current)
    • Re: System Config.?
      ... >If I go to system configuration utility, service tab. ... Many applications that put items into the startup ...
      (microsoft.public.windowsxp.perform_maintain)
    • Re: When to use Environment Variables?
      ... > I'm developing an application that needs some configuration ... > setting to be loaded on startup. ... > I'd like most settings to be loaded one time at startup, ... a running program. ...
      (comp.os.linux.development.apps)