On Thu, 2005-01-13 at 10:18 -0500, Dan Williams wrote: > On Wed, 2005-01-12 at 23:25 -0600, Satish Balay wrote: > > On Wed, 12 Jan 2005, Sandy Pond wrote: > > > > > I see on last rawhide update that NetworkManager now requires bind and > > > caching-nameserver. But the named service (bind) was not turned on: > > > > > > $ /sbin/chkconfig --list named > > > named 0:off 1:off 2:off 3:off 4:off 5:off 6:off > > > > > > Is it supposed to be turned on for NetworkManager? > > > > I see this update for FC3 (not rawhide). > > > > Any idea why NetworkManager requires bind? > > It uses bind in a caching-nameserver functionality and named should > _not_ be turned on my default in this configuration. Use of bind as a > caching nameserver was done to work around deficiencies of nscd and > glibc and should allow user applications to be aware of changes > to /etc/resolv.conf faster, since the applications actually just talk to > 127.0.0.1 for the nameserver, and its the caching-nameserver that > actually does the heavy lifting when /etc/resolv.conf changes since > glibc isn't up to the task. > > Dan > So my FC3 machine tells me that there is an unresolvable chain of dependencies and doesn't install the updates. I have a standard workstation install. -- Will Backman Coastal Enterprises, Inc. The ozone layer or cheese in a spray can. Don't make me choose.