From: Robert L. Harris (Robert.L.Harris@rdlg.net)
Date: Mon May 06 2002 - 15:37:11 EDT
Ok, I got "attacked" a few times when I mentioned replacing our NIS+
with LDAP.
One of the main reasons being that no-one here knows/understands NIS+.
I've been digging into it to support our existing infrastructure until
management makes a decision. There are definitely some good points to
it. I've just hit one of the snags that is making management nervous.
Scenario:
NIS+ servers are Solaris 7.
NIS+ client is RedHat linux.
If I stop NIS+ services:
[root@bt1 .ssh]# /etc/init.d/nis.init stop
Stopping NIS+ services: [ OK ]
[root@bt1 .ssh]# nisls
prod1.company.com.:
org_dir
groups_dir
[root@bt1 .ssh]# nisls org_dir.prod1.company.com.
org_dir.prod1.evoke.com.:
passwd
group
auto_master
auto_home
bootparams
cred
ethers
hosts
mail_aliases
sendmailvars
netmasks
netgroup
networks
protocols
rpc
services
timezone
client_info
If I start NIS+ services:
[root@bt1 .ssh]# /etc/init.d/nis.init start
Starting NIS+ services: [ OK ]
[root@bt1 .ssh]# nisls
prod1.company.com.:
Can't list directory: Error in RPC subsystem
(to protect my company's security and my job, I changed the company
name).
I've tried restarting portmap on the linux box and all is running just
fine. Other NIS+ clients are working fine, no errors. Searching google
and sunsolve yielded no useful information.
:wq!
---------------------------------------------------------------------------
Robert L. Harris | Micros~1 :
Senior System Engineer | For when quality, reliability
at RnD Consulting | and security just aren't
\_ that important!
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
FYI:
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:17 EDT