|
Home > Archive > Red Hat Networking > May 2005 > NIS fun, specially with the networks map, in a RHEL3 box
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
NIS fun, specially with the networks map, in a RHEL3 box
|
|
| Mauricio Tavares 2005-05-09, 5:52 pm |
| RHEL3 fun here:
1) I am trying to set the machine as NIS client. So, I edited
/etc/yp.conf to declare the domain and server. But, when I try to start
ypbind, it complain it cannot find the domainame:
[root@warsaw raubtest]# /sbin/ypbind
domainname not set - aborting.
[root@warsaw raubtest]# pwd
does that mean it is not reading /etc/yp.conf? Solaris expects the
domain to be in /etc/defaultdomain. So does Suse and debian and a few
others, which makes my life very easy. In redhat, I find conflicting
info: on one side I read (say, in the ypbind manpage and in
http://www.linux-nis.org/nis-howto/HOWTO/) that I am supposed to put
that in /etc/yp.conf so ypbind can find it. Problem is that it doesn't.
On the other side, I google around (even
http://www.linux-nis.org/nis-howto/...oot.html#AEN568 of all
places states it) and find info on creating a NISDOMAIN=domain_name in
/etc/sysconfig/network.
2) If I force the domainname, as in,
[root@warsaw raubtest]# domainname my.domain
[root@warsaw raubtest]#
and start ypbind using the /etc/init.d/ypbind, I get it to work. Well,
almost, as it seems to have issues with the networks map:
[root@warsaw raubtest]# ypcat networks
No such map networks.byaddr. Reason: Internal NIS error
[root@warsaw raubtest]#
which makes me believe there could be something wrong in NIS in that
machine; I do know that map is exported -- I can see it in other
machines -- but it is the only one I cannot see in the redhat box. And,
I kinda need it. Suggestions?
--
Mauricio raub-kudria-com
(if you need to email me, use this address =)
|
|
|
|
|