On Tue, 2005-12-13 at 13:11 -0500, Dan Williams wrote: > On Tue, 2005-12-13 at 18:15 +0100, Stefan Scheler wrote: <snip> > > What's still to be done is to set up the nis domain name and modify yp.conf > > accordingly. This should probably placed somehow in the distribution > > specific > > backends (i don't know how distribution specific that task really is)? > > It likely will be distro-specific. I don't know if anyone has cooked up > a resolvconf-type thing to manage yp.conf yet, but surely fewer apps > fight over it than resolv.conf. It might be adequate to just not care > about this until we find out another tool that wants to write yp.conf as > well. The other issue is how to alert the system that yp.conf has > changed...
On FC and RHEL, you would need to modify /etc/sysconfig/network (to set the NISDOMAIN) and do a "service ypbind restart". It would be pretty gross, as ypbind would take a long time to timeout if there are problems. --- Bastien Nocera <[EMAIL PROTECTED]> _______________________________________________ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list