Solved

500K+ Users on Unix

Posted on 1997-05-22
5
206 Views
Last Modified: 2013-12-16
I'm looking for approaches for setting up a Unix System (Solaris) for an ISP to support 500K to several million users.  /etc/passwd and NIS+ don't seem designed for this kind of user load.  I'm looking for suggestions on how to
solve this problem or products that already do it.
It is a problem that has obviously been solved be some organizations like Netcom, Earthlink, etc.   Thanks.
0
Comment
Question by:jht
  • 3
  • 2
5 Comments
 
LVL 5

Accepted Solution

by:
n0thing earned 200 total points
ID: 1812240
NIS+ could handle it, netcom is using NIS+, AOL uses a mainframe.
Just install a NIS+ server for each point of access, divide
it into subdomain if load arises. I won't go into the technical
details of it. But you'll have to carefully plan your network architecture/design. I'm currently running NIS+ for over
600K users with minors problems.

Good luck,
n0thing
0
 

Author Comment

by:jht
ID: 1812241
Its not clear to me how to distribute users among NIS+ sub-domains.  If user 'aaa' is traveling, they might to connect to a POP anywhere in the country.  How then to decide which subdomain they are in?  Also users will want a simple email address like:  aaa@netcom.com -- how to does this mesh with putting the users in sub-domains?  How many users can be in a sub-domain? Perhaps I'm mis-understood the sub domain concept...

Was also wondering if users with large NIS+ systems like n0thing or Netcom are using the database system supplied with NIS+ or have replaced it with something else using the methods described in 'man nis_db'?

Thanks.
 
0
 
LVL 5

Expert Comment

by:n0thing
ID: 1812242
You could divide users by geographical regions. If you provide
shell access, users must have a physical point of access according to their geographical regions. Just add the user in
their "home" subdomain. Most provider or all of them charge more for "roaming" users. POP access stays the same way, once they access the Net from whereever they call, they could access their POP server, since the POP is on the Net.
For aaa@netcom.com it's no problem a mail gateway could simply route the mail to the local POP server. User from anywhere on the
net could simply access to the local.pop.netcom.com and get their
mails from there.
I use standard NIS database supplied with NIS+, i don't know about Netcom.
0
 

Author Comment

by:jht
ID: 1812243
In order for mail to aaa@netcom.com  to be routed to a local POP server, it means that "aaa" is unique across the entire netcom.com system.  i.e. a database of all netcom.com users much exist and when new users signup the database must be checked fo ensure the new user id is unique.  If you've got all the users in one NIS+ domain, this happens automatically.  If you've split them into subdomains, I don't understand how this would work.

None of the national ISPs I've used (netcom, AT&T Worldnet, Compuserve, ...) charge extra for roaming.  You can call into any of their nodes any time without advance notice.  
0
 
LVL 5

Expert Comment

by:n0thing
ID: 1812244
The database on the mail gateway is the main database. It contains basicly all the unique user ID. So a basic setup will be
1- Checking on the mail gateway to make sure that user does not
   exist.
2- Add the user on the local subdomain.
3- Add an alias on the mail gateway "netcom.com" to route any mails to "aaa@netcom.com" to "aaa@local.pop.netcom.com".

If they don't charge for roaming, then all their dial-up server
must query a same centralize PPP authentication server. This central server could be duplicated accross sites to handle the load. Centralize PPP authentication doesn't have to be NIS+. It could be of any scheme, flat passwd file, SecureID, it depends
on the hardware you use. So my PPP login passwd is not necessary
the same as my Unix account login password ... NIS+ is used to
handle Unix accounts and so on. PPP login/account could be handled on a different way, depending on the hardware you use.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Installing FreeBSD… FreeBSD is a darling of an operating system. The stability and usability make it a clear choice for servers and desktops (for the cunning). Savvy?  The Ports collection makes available every popular FOSS application and packag…
Introduction Regular patching is part of a system administrator's tasks. However, many patches require that the system be in single-user mode before they can be installed. A cluster patch in particular can take quite a while to apply if the machine…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now