[74] in Hesiod
Re: How do I use hesiod efficiently?
daemon@ATHENA.MIT.EDU (Greg Wohletz)
Mon Dec 23 16:29:00 1991
To: Randall Winchester <rsw@eng.umd.edu>
Cc: jh@efd.lth.se, hesiod@Athena.MIT.EDU
In-Reply-To: Your message of "Mon, 23 Dec 91 15:37:53 EST."
Date: Mon, 23 Dec 91 13:21:06 -0800
From: Greg Wohletz <greg@duke.cs.unlv.edu>
>1) restricting NFS mounts by groups of machines
>We then modified rpc.mountd to call a hes_resolve() routine instead
>of the NIS call. This allowes "netgroups" to work in /etc/exports.
>An example;
hmm, I keep putting off doing the same for ours due to lack of time,
It would be great if you could send me your diffs.
>2) restricting logins by groups of users.
>Login.c (and others like xdm) were modified to use a /etc/restrict
>file which contains a "NIS like" format for allowing or denying users
>by groups.
>An example;
We do something similar to this as well.
>A note here about hesiod_service/name_service. The size of the named
>databases get pretty large when you start putting information for
>every user's home, mailbox, and pwent. There are usually a lot more users
>then machines, so some consideration for RAM on ther hesiod servers is
>needed. I am assuming thousands of users here.
Just for reference, we have around 1000 users on about 100 machines,
right now the RSS of our primary nameserver is a little more than
3meg. That machine has about 24meg of RAM. We haven't had a problem.
--Greg
