This is what I get for playing too much GTA: Vice City instead of reading e-mail.
Instead of saying "what he said" to Ken's responses, here's my thoughts. On Tue, Jun 17, 2003 at 06:03:27PM -0400, [EMAIL PROTECTED] wrote: > On Tue, 17 Jun 2003, at 5:45pm, [EMAIL PROTECTED] wrote: > >> No. My understanding is that ypbind is only run on NIS clients, no? > > > > No. It's run on everything -- the server is, indeed, still a client > > Okay, I'm definitely confused now. > > Nothing I've seen anywhere says that NIS servers have to be NIS clients. > Indeed, I've generally gotten the impression that, while it is quite > possible to do that, it is also quite optional. > > References: > > The Linux NIS-HOWTO, section 9.1, states "If you want to restrict access > for users to your NIS server, you'll have to setup the NIS server as a > client as well ...", which implies that such a configuration is optional. That should probably be corrected, or have the implication changed. > My copy of "Managing NFS and NIS", by Hal Stern, page 23, says that the > NIS master should not include the "+::::::" entry in the /etc/passwd file. > On page 26, it states that NIS clients must have that entry. I have that book. It's actually a pretty poor book (ORA can be hit or miss at times, sad but true). Actually, NIS clients don't really require +:::::: anymore, or at least not in all cases. More appropriate would be /etc/nsswitch.conf. NIS provides a lot more than just passwd entries, and nsswitch.conf manages where the system looks for that information. > I'm not saying you're wrong. It is rather more likely I am > misunderstanding something somewhere. But I want to fix my understanding, > as well as the computer. :-) Then start ypbind. Even if you're not using it for authentication, you'll want it running. -Mark
pgp00000.pgp
Description: PGP signature