[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#704211: [release-notes] [wheezy] issues: NM conflicts with wicd-daemon, Gnome3 now depends on NM

On Sunday, April 07, 2013 12:50:14, Andrei POPESCU wrote:
> On Du, 07 apr 13, 12:10:28, Chris Knadle wrote:
> > On Sunday, April 07, 2013 02:22:17, Andrei POPESCU wrote:
> > > On Vi, 29 mar 13, 09:45:11, Chris Knadle wrote:
> > > > You will also need to recreate /etc/resolv.conf, as the contents of
> > > > this file is replaced by NetworkManager.
> > > 
> > > Isn't this done by wicd-daemon (maybe by restarting it)?
> > 
> > It doesn't.  Also keep in mind that wicd can be set for all kinds of
> > configurations, such that it may not touch this file even making a
> > connection. [I have what appear to be default settings, and this is the
> > behavior I see on my home network, for instance.]
> This doesn't sound right. Wicd has got to have some resolv.conf
> handling, otherwise it wouldn't be very useful. Maybe the maintainer can
> help out here?

wicd can use a dhcp client (dhcpcd, pump, dhclient, udhcpc, "automatic"), but 
doesn't necessarily have to.  (My settings are in "automatic" right now.)  But 
there are always some cases where /etc/resolv.conf aren't normally overwritten 
(and that's not something confined to wicd).

The warning about /etc/resolv.conf being replaced by NM is generic so that if 
a user has this case they can investigate and fix it.

  -- Chris

Chris Knadle

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: