steve@mrc-applied-psychology.cambridge.ac.uk (Steve Platt) (10/08/90)
We recently setup a new DECStation (whats that?!) and wanted it to be a slave NIS (yp) server. We run ypinit on the system and it seemed to go well, fetching maps from the master server, etc etc. Then I noticed that certain maps were missing, such as bootparams, netid, publickey and rpc. All of these I can understand except rpc, as they could be construed to be SUN specific; but not rpc surely. (by the way, we add "pc-nfs" to our rpc map, so a supplied /etc/rpc file wouldn't do, even if there were one!) So I checked against the SUN ypinit script - which did the same thing, no bootparams, netid, publickey or rpc maps get set up! I also checked the "ypxfr" scripts (1perday, etc) and they seem to keep exactly the same subset of NIS maps uptodate as the ypinit script sets up to start with (that makes sense, I guess). Bearing in mind that we might have other locally invented NIS maps (and not to mention the automounter maps) what do other people do when setting up a new slave NIS server? How would one go about putting "all" the maps out to all servers (by the way, we once managed to see one NIS server with an out-of-date "ypservers" map - that caused fun!). Steve Platt Tempus Fugitive MRC Applied Psychology Unit 15 Chaucer Road Cambridge CB2 2EF