home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!hal.com!decwrl!access.usask.ca!ccu.umanitoba.ca!mills
- From: mills@ccu.umanitoba.ca (Gary Mills)
- Newsgroups: comp.sys.sun.admin
- Subject: Re: how to determine if ypservices available
- Message-ID: <1992Aug25.181325.15965@ccu.umanitoba.ca>
- Date: 25 Aug 92 18:13:25 GMT
- References: <1992Aug25.121930.11832@iplmail.orl.mmc.com>
- Organization: University of Manitoba, Winnipeg, Canada
- Lines: 22
-
- In <1992Aug25.121930.11832@iplmail.orl.mmc.com> chucks@iplmail.orl.mmc.com (Chuck Strickland) writes:
-
- > this works great. the problem is that when the system
- > comes back on the net, sometimes after a couple of months, the yp maps
- > a extremely out of date.
-
- What I do to avoid the problem of out-of-date NIS maps on the slaves is
- to run yppush every night on the NIS master. Sun recommends running
- ypxfr on the clients, but I find yppush simpler, and it will only
- initiate an ypxfr if the maps are out of date. Here's my script:
-
- #!/bin/sh
- # yppushall: push all NIS maps to all NIS slaves
-
- for MAP in `ypwhich -m | cut -d' ' -f1`
- do
- /usr/etc/yp/yppush $MAP
- done
-
- #!/end
- --
- -Gary Mills- -Networking Group- -U of M Computer Services-
-