*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->IRIX man pages              
 ypmake(1) -- rebuild and distribute NIS databases
    On NIS master machines, ypmake uses the file /var/yp/mdbm_parse and the optional file /var/yp/local.make.script to build the network information service (NIS) databases. With no arguments, ypmake creates mdbm(3B) databases for any NIS maps that are out-of-date and then executes yppush(1M) to notify slave servers that there has been a change. If invoked with map, ypmake updates that map only. Typing ypmake passwd creates and yppushes the password database (assuming it is out-of-date). Likewise, y...
 ypmatch(1) -- print key values in NIS map
    ypmatch prints the values associated with one or more keys from the network information service (NIS) map (database) specified by a mname, which may be either a mapname or an map nickname. Multiple keys can be specified; the same map will be searched for all. The keys must be exact values insofar as capitalization and length are concerned. No pattern matching is available. If a key is not matched, a diagnostic message is produced....
 yppasswd(1) -- change NIS login password
    yppasswd changes (or installs) a password associated with the user name (your own name by default) in the network information service (NIS) passwd databases. The NIS password may be different from the one for the same user in the local /etc/passwd file. yppasswd prompts for the old NIS password and then for the new one. The caller must supply both. The new password must be typed twice, to forestall mistakes. New passwords must be at least four characters long if they use a sufficiently rich alph...
 yppoll(1) -- show the version of the NIS map on the NIS server
    yppoll asks a ypserv process what the order number is and which host is the network information service (NIS) master server for the map mapname. If the server is a v.1 NIS protocol server, yppoll uses the older protocol to communicate with it. In this case, it also uses the older diagnostic messages in case of failure.
 yppush(1) -- force propagation of a changed NIS map
    yppush copies a new version of the specified NIS map from the master NIS server to the slave NIS servers. It is normally run only on the master server by ypmake(1M) after the master databases are changed. It first constructs a list of NIS server hosts by reading the ypservers map within the domain. Keys within the ypservers map are the hostnames of the domain's NIS servers. A ``transfer map'' request is sent to the NIS server at each host, along with the information needed by the transfer age...
 ypset(1) -- point ypbind at a particular NIS server
    ypset tells ypbind(1M) to get the network information service (NIS) for the specified domain from the ypserv process running on server. If server is down, or isn't running ypserv, this is not discovered until an NIS client process tries to get a binding for the domain. At this point, the binding set by ypset will be tested by ypbind. If the binding is invalid, ypbind attempts to rebind for the same domain. By default, ypbind does not allow ypset operations from local or remote hosts. ypset retu...
 ypupdated(1) -- server for changing NIS information
    ypupdated is a daemon that updates information in the network information service (NIS), normally started up by inetd(1M). ypupdated consults the file updaters(4) in the directory /var/yp to determine which NIS maps should be updated and how to change them. By default, the daemon requires the most secure method of authentication available to it, which currently is AUTH_UNIX. The DES authentication method is not implemented at the time....
 ypwhich(1) -- print the NIS server or map master hostname
    ypwhich tells which network information service (NIS) server supplies NIS services to an NIS client, or which server is the master for a map. If invoked without arguments, it prints the NIS server for the local machine. If hostname is specified, that machine is queried to find out which NIS server it is using. Refer to ypfiles(4) and nis(1M) for an overview of NIS.
 ypxfr(1) -- transfer an NIS map from some NIS server to here
    ypxfr moves a network information service (NIS) map to the local host by making use of normal NIS services. It creates a temporary map in the directory /var/ns/domain/domain (which must already exist), fills it by enumerating the map's entries, fetches the map parameters (master and order number) and loads them. It then deletes any old versions of the map and moves the temporary map to the real mapname. If ypxfr is run interactively, it writes its output to the terminal. However, if it is invok...
 yp_bootparam(1) -- update the NIS bootparams database
    yp_bootparam is the user interface tool to update the NIS bootparams(4) database directly on client workstation without running on ypmaster. yp_bootparam uses the ypupdated(1M) service on ypmaster to update the bootparams database. User can either add an entry to database or delete an entry. As long as the hostname is registered in the NIS hosts database and the bootparam entry does not exist, the user can always add an entry to the bootparams database. In this process, a security key can be req...
 yp_host(1) -- update NIS "hosts" database
    yp_host is the user command to update the NIS hosts database directly from a client workstation. yp_host uses the ypupdated(1M) service on the NIS master to update the NIS hosts database. The single-threaded nature of ypupdated(1M) guarantees the database will remain consistent even when multiple updates are attempted at the same time. Users can add, change, or delete an entry to the database. As long as the hostname is not used in the current database, there are no restrictions for creating an ...
<<  [Prev]  76  77  78  79  80  81  82  83  84  85  86  87  88  89  90  91  92  93  94  95  96  
[Next]  >>
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service