10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
This is the very simple and easy to understand.
How to Disable SSH Logins on a Linux Box?
Hello and Welcome to The UNIX and Linux Forums!
DO NOT hijack others' threads; create a new one with a meaningful and adequate title.
Please read the our FAQ on how to post new threads in the... (1 Reply)
Discussion started by: Bhargavice
1 Replies
2. Solaris
Hi guys,
In my Sol-10 i setup NIS server following the oracle doc and setup a Linux as NIS client all went ok.
I added another Sol-10 and configure it as a NIS slave server following the oracle doc again. and added the server on the yp.conf on my NIS client
How do i test if my NIS slave... (3 Replies)
Discussion started by: batas
3 Replies
3. Red Hat
After configuring the NIS server in my machine (RHEL 5.4)
i create two NIS users user1 and user2 and one local user
when i login to user1 and user2 from client machine i am not able to login
for login to user1 and user2 first i have to login to local user and then i am able to login to... (4 Replies)
Discussion started by: vipinkumarr89
4 Replies
4. Solaris
Hey Guys,
I need your help.
My NIS server filesystem is 100%, the NIS is running under solaris 10.
I am affraid if the server stops, it wont come up again.
Please help. (4 Replies)
Discussion started by: andrevicente
4 Replies
5. Solaris
Hi All,
I have a client already binded with a NIS master server. Now, I want to bind this particular client to one of NIS slave. How to do it?
Thanks,
Deepak (2 Replies)
Discussion started by: naw_deepak
2 Replies
6. AIX
Hi all,
Kindly can help to config the NIS master server in AIX 5.3 ?
Many Thanks.
My procedure:
smit yp -> Change NIS Domain Name of this Host
smit yp -> Configure / Modify NIS -> Change / Show Characteristics of Master Server Configuration
The "Current domain anme of this host" &... (1 Reply)
Discussion started by: tyu
1 Replies
7. Solaris
Hi, all.
I have a Solaris client here needs to bind to NIS server in another subnet. Following is the configuration i made on the client,
1) edit /etc/inet/hosts to add an entry of the NIS server -- nserver01
2) execute `domainname` to set local NIS domain to the domain of the NIS server.... (1 Reply)
Discussion started by: sn_wukong
1 Replies
8. UNIX for Advanced & Expert Users
I am changing the IP on my NIS server. Are there any files that need to be changed on my other servers that are using NIS? (1 Reply)
Discussion started by: calamine
1 Replies
9. UNIX for Advanced & Expert Users
We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave.
We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation.
However, no matter what i do, the SUSE machines will not talk to the NIS Servers.
If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Discussion started by: fishsponge
1 Replies
10. UNIX for Dummies Questions & Answers
How can I remove a replica server from my NIS+ domain? From reading the man page, it looks like this will work
nisrmdir -s hostname org_dir.domain.com.
But it comes back with
remove "org_dir.domain.com."?
I am afraid that will remove all the tables associated with the domain, not just the... (1 Reply)
Discussion started by: 98_1LE
1 Replies
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)