64K limit is due to the fact that userids have that particular precision.
0xFFFF is the ceiling value for PIDs and UIDs in Linux, unless you use
kernel 2.4..
On Wed, 29 Nov 2000, Kelsey Hartigan Go wrote:
> The 64K limit is due to the array handling the file...so if you have 3 files,
> then that would mean 3 64K limit. Now that remains to be seen...
> I'm just explaining based on my knowledge on the passwd file.
>
>
>
> On 28 Nov 00 at 23:22, Ina Patricia Lopez wrote:
>
> >
> > actually, i already have separate passwd/shadow files for each domain.
> > im just curious if each domain can have 64K users.
> >
> > thanks.
> >
> > --- "Ian C. Sison" <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > On Tue, 28 Nov 2000, Michael J. Maravillo wrote:
> > >
> > > > On Mon, Nov 27, 2000 at 09:36:17PM -0800, Ina Patricia Lopez wrote:
> > > > >
> > > > > Question 1: am i still limited with the 64K limit for virtual
> > > passwd
> > > > > and virtual shadow files of each domain?
> > > >
> > > > Note that that's 64K for all domains, not for each. Each user on
> > > > your system maps to one unique system userid -- which currently has
> > > > a max of 16-bits on most(?) Linux systems. See "man getpwent"
> > > > where uid_t is an unsigned int...
> > >
> > > You can also try cyrus-imap which does not have the 64K limitation,
> > > as
> > > users may be stored in a database.
> > >
> > >
> > > > Or, you can go the virtual route of storing all user info in some
> > > > directory storage like LDAP -- as what Victor mentioned
> > > > previously. Mailbox locations, passwords, etc. are looked up
> > > > from the directory. With this setup, mostly likely you'll be
> > > > using only one system userid for all your virtual users. No
> > > > 16-bit limit, therefore unlimited number of users. Some links
> > > > you might want to check out:
> > > >
> > > > - LDAP_README of the Postfix distribution
> > > > - qmail-ldap: http://www.nrg4u.com/
> > > > - ISPman: http://ispman.sourceforge.net/
> > > >
> > > > > Question2: now that virtual email hosting seems to be working now
> > > > > (using pop), are the lines below still applicable??
> > > > >
> > > > > > [EMAIL PROTECTED] user1@localhost
> > > > > > [EMAIL PROTECTED] user2@localhost
> > > > > > [EMAIL PROTECTED] user3@localhost
> > > >
> > > > These are used by sendmail, not the POP server. Without these,
> > > > your SMTP server won't know to which local user an incoming
> > > > e-mail is for -- specially in cases (your example above) where
> > > > you have multiple and same username parts but with different
> > > > domains.
> > >
> > > The limitation with a one-box, many domains solution is that you have
> > > only
> > > one passwd file for all of the domains, so you can't support
> > > [EMAIL PROTECTED] and [EMAIL PROTECTED], unless you alias them,
> > > and
> > > will be a pain to maintain.
> > >
> > > Alternately for a more wholelistic approach to virtual domains, check
> > > out
> > >
> > > http://www.prongs.org/virtfs/
> > >
> > > which will allow you to have one passwd file for each domain.
> > >
> > >
> > >
> > >
> > > _
> > > Philippine Linux Users Group. Web site and archives at
> > > http://plug.linux.org.ph
> > > To leave: send "unsubscribe" in the body to
> > [EMAIL PROTECTED]
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Shopping - Thousands of Stores. Millions of Products.
> > http://shopping.yahoo.com/
> >
> > _
> > Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
> > To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
> >
>
> _
> Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
> To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
>
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
