SCIENTIFIC-LINUX-USERS Archives

August 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Konstantin Olchanski <[log in to unmask]>
Reply To:
Konstantin Olchanski <[log in to unmask]>
Date:
Sat, 8 Aug 2015 23:24:35 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
On Sat, Aug 08, 2015 at 04:23:50PM -0400, Nico Kadel-Garcia wrote:
> 
> So, why are you using NIS?
> 

Migration of user login from NIS to LDAP seems to be pretty well documented and could be done in less than 1 day per NIS cluster (we have around 5-10 NIS clusters around here).

But NFS mounts (autofs) and NFS export (netgroup) migration from NIS to LDAP seems to be pretty much impossible.

Yes there are web sites that explain how to mutate LDAP and autofs to make them talk to each other,
but none of the instructions seem to be straightforward. Probably takes about 5 days of reading LDAP manuals
plus 5 days of setting up a test cluster to figure everything out.

Certainly the Red Hat manuals only talk about using LDAP for user login management, not a word about NFS/autofs.

Then, redundant NIS configuration is trivial (with NIS slave servers). Redundant LDAP configuration requires another couple of week of reading LDAP manuals and playing with test clusters, yes?

It would probably take less time to reimplement NIS using perl/scp/rsync (to copy /etc files from master to client)
than to figure out all this LDAP stuff.

If "L" in LDAP stands for "light", I wonder what the "heavy" one looks like.

-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada

ATOM RSS1 RSS2