Re: NIS vs. Network Manager
On Tue, Mar 20, 2007 at 07:13:17PM +0000, Mark Brown wrote:
> On Fri, Mar 09, 2007 at 08:01:00PM +0000, Mark Brown wrote:
> > Recent versions of NIS have included support in ypbind for Network
> > Manager. This support currently causes ypbind to disable NIS client
> > functionality when Network Manager reports that the computer is
> > disconnected. Unfortunately, Network Manager is frequently installed on
> > systems where it is not in use and which have network configurations
> > which it does not support. On many of these systems the result is that
> > Network Manager runs and reports that the system is disconnected from
> > the network, rendering ypbind unusable.
> Please consider nis 3.17-6 for etch. It works around this problem by
> default using this message:
> > - Disable Network Manager support at runtime by default. The
> > disadvantage here is that this would be done by disabling a
> > frequently edited conffile so many users would not pick up the new
> > default on upgrade and would therefore be affected by the integration
> > problems.
> (in actual fact it's a configuration file, not a conffile.) I'll submit
> an update to the release notes shortly.
Unblocked. (dbus support in nis? <shudder>)
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/
Reply to: