Prevent accidental push of yp maps from slave servers

7 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Help with accidental endless loop

I was practicing writing simple loops as I am a new bash user and I created this script, which turned out to be an endless loop where the echo output does not stop and I do not see where my mistake is. #!/bin/bash echo 'enter a number from 1 to 100' read number while do ...

2. UNIX for Dummies Questions & Answers

/proc/pid/maps

I think the libc.so is shared between processes, because it is a shared library and OS is engaged for saving memory. But, below, the maps of bash, shows r-xp and r--p rw-p attributes to libc.so which mean private memory space. Can anybody explain this for me? :)cat /proc/$$/maps...

3. Shell Programming and Scripting

Prevent wrong user from using shell script for multiple remote servers

Hi, I am running a shell script from a central server to multiple remote servers using the following code: application_check() { # Linux/UNIX box with ssh key based login SERVERS=`cat /tmp/server-details` # SSH User name USR="user" # create new file > /tmp/abc.log # connect...

4. UNIX for Dummies Questions & Answers

Accidental deletion of root account

I had created a root account when I installed the Centos 5 into my system. But now the problem I'm facing is that I accidently deleted the root user account in my system. Is there a way to recreate the root account in the system now, without reinstalling the OS? Pls help.

5. UNIX for Dummies Questions & Answers

Protect .profile from accidental delete

Hi, Is there a way to protect users from deleteing their .profile ? For the majority of our users I created a captive login by a .profile that starts a menu-script. In this menu a user can only start our applications and logoff. This prevents users from getting to the unix-prompt. ...

6. Shell Programming and Scripting

How to remove accidental file

Hi, I have a strange problem. I accidentally created a file named ${1}_$(date+%Y%m%d) and when i am trying to remove it I am getting this error . Can any one suggest me how i can remove this accidental file.

7. UNIX for Advanced & Expert Users

NIS Maps

Hello.. I stink at NIS! :) Im having a problem with NIS on solaris 2.X. / SPARC I have some maps that are exported to all clients in the domain. Now I setup a new server and add it as a nis client to the domain. On the NIS server there is a auto_direct map that mounts /usr/local . This is...

LEARN ABOUT FREEBSD

rpc.ypxfrd

RPC.YPXFRD(8)						    BSD System Manager's Manual 					     RPC.YPXFRD(8)

NAME

     rpc.ypxfrd -- NIS map transfer server

SYNOPSIS

     rpc.ypxfrd [-p path]

DESCRIPTION

     The rpc.ypxfrd utility is used to speed up the distribution of very large NIS maps from NIS master to NIS slave servers.  The normal method
     for transferring maps involves several steps:

	   o   The master server calls yppush(8) to inform the slave servers to start a transfer.

	   o   The slave servers invoke ypxfr(8), which reads the entire contents of a map from the master server using the yp_all() function.

	   o   The ypxfr(8) program then creates a new map database file by using the db(3) library hash method to store the data that it receives
	       from the server.

	   o   When all the data has been retrieved, ypxfr(8) moves the new file into place and sends ypserv(8) on the local machine a
	       YPPROC_CLEAR to tell it to refresh its database handles.

     This process can take several minutes when there are very large maps involved.  For example: a passwd database with several tens of thousands
     of entries can consume several megabytes of disk space, and it can take the db(3) library package a long time to sort and store all the
     records in a hash database.  Consider also that there are two sets of map files: master.passwd.by{name,uid} and passwd.by{name,uid}.

     The rpc.ypxfrd utility speeds up the transfer process by allowing NIS slave servers to simply copy the master server's map files rather than
     building their own from scratch.  Simply put, rpc.ypxfrd implements an RPC-based file transfer protocol.  Transferring even a multi-megabyte
     file in this fashion takes only a few seconds compared to the several minutes it would take even a reasonably fast slave server to build a
     new map from scratch.

     The rpc.ypxfrd utility uses the same access restriction mechanism as ypserv(8).  This means that slave servers will only be permitted to
     transfer files if the rules in the securenets database permit it (see ypserv(8) for more information on securenets).  Furthermore, only slave
     servers using reserved ports will be allowed to transfer the master.passwd maps.

OPTIONS

     The following option is available:

     -p path
	     This option can be used to override the default path to the location of the NIS map databases.  The compiled-in default path is
	     /var/yp.

FILES

     /var/yp/[domainname]/[maps]       The NIS maps for a particular NIS domain.

SEE ALSO

     yp(8), yppush(8), ypserv(8), ypxfr(8)

AUTHORS

     Bill Paul <wpaul@ctr.columbia.edu>

BUGS

     The FreeBSD ypxfrd protocol is not compatible with that used by SunOS.  This is unfortunate but unavoidable: Sun's protocol is not freely
     available, and even if it were it would probably not be useful since the SunOS NIS v2 implementation uses the original ndbm package for its
     map databases whereas the FreeBSD implementation uses Berkeley DB.  These two packages use vastly different file formats.	Furthermore, ndbm
     is byte-order sensitive and not very smart about it, meaning that am ndbm database created on a big endian system cannot be read on a little
     endian system.

BSD
								   June 2, 1996 							       BSD

UNIX for Advanced & Expert Users