[107] in Hesiod
How do you implement Hesiod services?
daemon@ATHENA.MIT.EDU (SAM@CSI.compuserve.com)
Thu Oct 29 21:15:09 1992
Date: 29 Oct 92 21:02:03 EST
From: <SAM@CSI.compuserve.com>
To: <hesiod@Athena.MIT.EDU>
I've been looking into Hesiod to help centralize the administration of
a dozen or so Unix boxes that I've got running. I plan on using it
initially to replace /etc/passwd and /etc/group, and in the future, I
might add some of the other commonly used tables like /etc/services,
/etc/fstab, and others. (I'm also looking into Moira at some moment in
the near future.)
As always, questions arise:
* I have replaced getpwnam(3), getpwuid(3), getgrnam(3), and
getgrgid(3) in libc. Is this going to cause many problems? Is this
the preferred way of handling this, or do people normally place the
Hesiod calls directly in the source?
* I plan on relinking all of my utilities with the new libc. I do not
forsee any major problems, however, I'm curious if this is the
approach taken by others. What kind of problems am I in for? Are
there any utilities that should not be Hesiodized? (ie, login, su?)
* How do you handle getpwent(3) and getgrent(3) which want to
sequentially scan through the passwd and group database?
* How do you perform /etc/{passwd,group} lookups? Do you hit the disk
file first and if that fails try Hesiod, or Hesiod then disk?
* Finally, does anyone have any examples/source that they're able to
share? Why reinvent the wheel...
Thanks
- Sam
--
Sam Neely, CompuServe Incorporated +1 614 457 8600 (voice)
5000 Arlington Centre Blvd, Columbus, OH 43220 +1 614 457 0348 (FAX)
Electronic Mail: InfoPlex: >CSI:SAM Internet: SAM@CSI.COMPUSERVE.COM
To err is human, to forgive is against company policy.
