|
|
Migrating password file to new freebsd server
|
|
yppasswdd(1M) yppasswdd(1M) NAME
yppasswdd: rpc.yppasswdd - daemon for modifying Network Information Service passwd database SYNOPSIS
passwd_file log_file] [arg1 arg2 ...]] directory] log_file] [arg1 arg2 ...]] Remarks The Network Information Service (NIS) was formerly known as Yellow Pages (yp). Although the name has changed, the functionality of the service remains the same. DESCRIPTION
The daemon handles password change requests from (see yppasswd(1)). It changes a password entry in the passwd and shadow files. The passwd and shadow files provide the basis for the passwd.byname and passwd.byuid maps. Entries in the passwd or shadow files are changed only if the password presented by matches the encrypted password of the entry. All password files are located in the directory. If the option is given, the passwd or shadow files are placed under the directory path that is the argument to should be executed only on the master Network Information Service (NIS) server for the passwd database (map). The daemon is not executed by default, nor can it be started by (see inetd(1M)). To enable automatic startup of at boot time, the variable should be set to 1 in file on the master NIS server. The daemon in HP-UX 11i version 3 supports the shadow mode. The system can be converted to shadow mode by using and reverted by using The variable must be set to 1 in file on the master NIS server to support the shadow mode in NIS. The server does not insist on the presence of a shadow file unless there is no option present or the directory named with the option is Options recognizes the following options and command-line arguments: Log diagnostic and error messages to log_file. These messages are not available if is started without the option. Information logged to the file includes date and time of the message, the host name, process ID and name of the function generating the message, and the message itself. Note that different services can share a single log file because enough information is included to uniquely identify each message. If these are given, then these fields may not be changed remotely using is HP specific. After the password or shadow file is modified, and if using the option, executes to update the NIS passwd database (see ypmake(1M)). Any arguments following the flag are passed to To ensure that the passwd map is rebuilt to contain the new password and all slave NIS servers have their passwd maps properly updated to include the change, always use the option to but do not use the argument to The directory input specifies which directory contains the passwd file (and the shadow file when the system is in shadow mode). Note that the directory specified must contain the file named "passwd". If shadow mode is enabled, then the directory specified must contain a file called "shadow". EXAMPLES
Assume the daemon is started on the master NIS server as follows: This indicates that the ASCII file from which the NIS passwd database is built is When this file is updated by a request from the NIS passwd database is rebuilt and copied to all slave NIS servers in the master's NIS domain (see domainname(1)). Log messages are written to the file WARNINGS
uses lock file to get exclusive access to passwd_file when updating it. The file may persist if passwd_file is being updated and o The system crashes or o is killed using (see kill(1) and signal(2)). File must be removed before can function properly again. also uses when updating (see vipw(1M)). As a result, competes with when it updates passwd_file if passwd_file is AUTHOR
was developed by Sun Microsystems, Inc. FILES
lock file used when updating passwd_file SEE ALSO
domainname(1), kill(1), yppasswd(1), inetd(1M), vipw(1M), ypmake(1M), signal(2), yppasswd(3N), passwd(4), publickey(4), ypfiles(4), pwconv(1M), pwunconv(1M), shadow(4). yppasswdd(1M)
