NIS problem
in [RedHat]
|
From: Art Werschulz on 30 Mar 2007 09:23 Hi. I am sorry to repost this. However, I have been told that comp.os.linux.misc is a quasi-bogus newsgroup. Since I had directed all responses to comp.os.linux.misc, I'm afraid that any responses will simply go into /dev/null. Running Fedora Core 6 on an Intel x86 platform ... The hard drive on our NIS master server just died. We are in the process of rebuilding the server. (We have no slave servers.) On the NIS master server, I did /usr/lib/yp/ypinit -m I took the default action of only using the hostname of our one NIS server. I then did service ypbind start service ypxfrd start (The latter was to play it safe; we haven't used it before.) The output of "rpcinfo -p localhost" is program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 654 status 100024 1 tcp 657 status 100009 1 udp 969 yppasswdd 100021 1 tcp 44909 nlockmgr 100021 3 tcp 44909 nlockmgr 100021 4 tcp 44909 nlockmgr 100007 2 udp 639 ypbind 100007 1 udp 639 ypbind 100007 2 tcp 642 ypbind 100007 1 tcp 642 ypbind 600100069 1 udp 688 fypxfrd 600100069 1 tcp 690 fypxfrd 100004 2 udp 983 ypserv 100004 1 udp 983 ypserv 100004 2 tcp 986 ypserv 100004 1 tcp 986 ypserv This looks pretty good. Moreover, on the master server, the commands ypwhich ypmatch joeuser passwd getent joeuser passwd give the expected results. I then go over to an NIS client. (Please note that nothing evil has happened to the client.) The command service ypbind start gives me Turning on allow_ypbind SELinux boolean Binding to the NIS domain: [ OK ] Listening for an NIS domain server.................... Turning off allow_ypbind SELinux boolean [FAILED] Note that the client *can* ping the server. What have I forgotten to do? Many thanks! -- Art Werschulz (agw STRUDEL comcast.net)
|
Pages: 1 Prev: NIS problem Next: Root EXT3 FS move All files to Lost+Found after FSCK |