Bug 3197 - nis bugs
nis bugs
Product: Red Hat Linux
Classification: Retired
Component: ypserv (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Jay Turner
Depends On:
  Show dependency treegraph
Reported: 1999-06-01 16:02 EDT by aapuch
Modified: 2015-01-07 18:37 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-06-01 16:51:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description aapuch 1999-06-01 16:02:48 EDT
here is my set up
rpc.yppasswdd --debug
rpc.yppasswdd - NYS YP server version (with
rpc.yppasswdd already running (pid 2652) - exiting
[root@nis yp]# kill -9 2652
[root@nis yp]# rpc.yppasswdd --debug
rpc.yppasswdd - NYS YP server version (with

[1]+  Stopped                 rpc.yppasswdd --debug
[root@nis yp]# bg
[1]+ rpc.yppasswdd --debug &
[root@nis yp]# yppasswd
yppasswd: can't find the master ypserver: Can't bind to
server which serves this domain

Is there some thing I am missing ??

also if I change the passwd on a user

passwd just x out the password !!!

this is not good !!!

I am done playing with the nis stuff,

I am going to hesiod and kerb !!!
Comment 1 Jeff Johnson 1999-06-01 16:51:59 EDT
There are several problems that have been fixed in yppasswd. Try
ypserv- or later for those fixes.

However, you probably need to configure your yp server correctly. That
requires doing at least
	domainname whatever	# make sure your domain is correct
	pwconv			# use shadow passwords
	grpconv			# and convert /etc/group too
	cd /var/yp		# update all the maps
	edit /etc/yp.conf	# to identify the server and domain
	/etc/rc.d/init.d/ypserv	start	# start the server
	/etc/rc.d/init.d/ypbind start	# start the client
	... the ypbind client should find the yopserv server here ...
	/etc/rc.d/init.d/yppasswd start	# start the ypppasswd server

Note You need to log in before you can comment on or make changes to this bug.