[arch-projects] [netcfg] Reviewing old code: custom control paths

Rémy Oudompheng remyoudompheng at gmail.com
Thu Jul 5 02:38:03 EDT 2012

On 2012/7/3 Jouke Witteveen <j.witteveen at gmail.com> wrote:
> Dear Rémy,
> I came across commit a1fc1 to netcfg. It refers FS#24949 both in the
> commit message and the comments. That bug looks completely unrelated.
> Can you elaborate why it was/is needed to support custom control
> paths? Dealing with WPA_CTRL_PATH makes for messy code, currently. I
> guess if we want to go with supporting it, someone should write a
> wpa_cli wrapper that
> 1) uses WPA_CTRL_PATH if it is set, or extract it (currently
> connections/ethernet and connections/wireless duplicate code)
> 2) else determines WPA_CTRL_PATH from th profile that is active on the interface
> 3) else uses a default value

WPA_CTRL_PATH was not meant to be configurable (is it documented?).

The relevant bug is https://bugs.archlinux.org/task/24929 (sorry for
the typo). It was for the combination of move to /run and allowing
custom configuration files for wpa_supplicant.


More information about the arch-projects mailing list