home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.sysv386
- Path: sparky!uunet!wupost!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uchinews!machine!chinet!ignatz
- From: ignatz@chinet.chi.il.us (Dave Ihnat)
- Subject: Re: 386 Unix - is 5,000 logins realistic?
- Message-ID: <BxznqD.MIo@chinet.chi.il.us>
- Summary: Well, disk access should be better...
- Sender: Dave Ihnat
- Organization: Chinet - Public Access UNIX
- References: <1992Nov18.031323.8045@toolz.uucp> <1992Nov18.221254.13744@openage.openage.com>
- Date: Fri, 20 Nov 1992 00:23:00 GMT
- Lines: 30
-
- In article <1992Nov18.221254.13744@openage.openage.com> gryphon@openage.openage.com (The Golden Gryphon) writes:
- >todd@toolz.uucp (Todd Merriman) writes:
- >
- >
- >>Is it realistic to support about 5,000 logins with a 386 Unix?
- >
- >Passwd search times will make logging in slow. 5000 users in 1 group may make
- >/etc/group unuseable, because they all have to be on one line. You may be able
- >to fix that with "\"'s at the end of every x number of users.
- >
- Frankly, unless I have an overwhelming reason to put everyone in the same
- group, I give every login its own group. This aids security, while I can allow
- group access via 'newgrp' or other such ploys.
-
- I would suggest that you order both your group and passwd files by use; that
- way, the most frequent users get the fastest login.
-
- >You will also have directory search problems if all their home directories
- >reside in the same place. You can changes this and keep different parent
- >directories based on their names or something. It will probably be best to
- >subdivide them further.
-
- Possibly; although on BSD, Sun, or SVR4 systems the hashed directory structure
- will mitigate this problem greatly.
-
- Cheers,
-
- Dave Ihnat
- ignatz@homebru.chi.il.us (preferred return address)
- ignatz@chinet.chi.il.us
-