[Bug 135909] Re: wpa_supplicant isn't killed on unplug

[Alan Jenkins]

"Will make it apply to the interface whenever <interface> shows up"

 - also confused me a bit.  It's *not* equivalent to allow-hotplug.
auto/allow-auto blocks the boot process if the interface is unplugged
when you reboot.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/135909

Title:
  wpa_supplicant isn't killed on unplug

Status in “ifupdown” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: wpasupplicant

  I have a USB wireless wireless adaptor.  I have a use case which is
  not well suited to NetworkManager - single AP and with a multi-user
  system.  So I set it up using "wpa-" options in
  /etc/network/interfaces instead, and added a "mapping hotplug" section
  in case a user should unplug the adaptor and replug it for some reason
  :-).

  So AFAIK what should happen is a copy of wpa_supplicant is started
  when the device is detected, and killed when it is removed.  The first
  bit works, and I have wonderful hotplug goodness.

  Unfortunately the killing on removal doesn't seem to work properly.
  For me it's mainly a matter of tidyness and correctness.  However the
  surplus process is consuming resources: in particular it shows up on
  powertop as being responsible for 3 wakeups per second - and the
  target for efficient idling is somewhere under 10 per second.

  I know which scripts (ifupdown hooks) are supposed to be taking care
  of this , but I haven't debugged it.  Any hints on debugging this sort
  of thing would be appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/135909/+subscriptions