Differences between revisions 3 and 4
Revision 3 as of 2012-11-14 23:13:15
Size: 1008
Editor: MichaelBiebl
Comment:
Revision 4 as of 2012-11-15 00:38:24
Size: 1041
Editor: MichaelBiebl
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Running multiple connection managers at the same time can lead to unwanted and unexpected behaviour. It is obvious when both try to manage the same network interface. But even if they are controlling different interfaces, you can still run into problems, like:
 * Writing directly to a shared ressource like /etc/resolv.conf (without an arbiter as e.g. resolvconf)
Running multiple connection managers at the same time can lead to unwanted and unexpected behaviour. It is obvious when there is more than one trying to manage the same network interface. But even if they are controlling different network interfaces, you can still run into problems, due to:
 * Writing directly to a shared ressource like /etc/resolv.conf (without a gatekeeper as e.g. resolvconf)

Problem statement

Running multiple connection managers at the same time can lead to unwanted and unexpected behaviour. It is obvious when there is more than one trying to manage the same network interface. But even if they are controlling different network interfaces, you can still run into problems, due to:

  • Writing directly to a shared ressource like /etc/resolv.conf (without a gatekeeper as e.g. resolvconf)
  • Running multipe instances of services like wpa_supplicant.

Affected packages: connman, network-manager, wicd. Try to detect such situations and let the user chose which option he wants to enable.

Proposal

  • Shared debconf template
  • in postinst, show debconf prompt if >1 connection managers are found

  • Detection if service is installed and/or active/enabled:
    1. test -f /usr/sbin/<daemon>, where daemon=NetworkManager|connman|wicd

    2. test -f /etc/rc2.d/S??<service>, where service=network-manager|connman|wicd

    3. test if D-Bus name is taken