Jimmy Ott wrote:
you are right, if the homedirectory attribute is also used for other
things. but i just hosting email virtual users on my server, and they
don't need the homedirectory attribute. so i thought to keep the ldap
directory tighter and without any duplicate information.
at the moment i use the homedirectory attribute exactly like you described.
Well, do a quick basic cost/benefit analysis.
First, what are the ongoing costs of your current practice? Is there
extra effort involved in filling in the homeDirectory attribute? Do you
have to regularly check for discrepancies between homeDirectory and the
mail address? Are there other operating problems caused by storing
homeDirectory? I'm inclined to believe that there aren't, and your
costs are roughly nil.
Then consider the cost of the change. First, you're investing your time
researching the level of support for the change among all of the
software currently using your directory. Then there will be the effort
of retooling your management software, testing all of your applications,
and rolling out into production.
And what's your benefit? You're going to save about 50 bytes per user
in your directory. The return on that investment seems exceedingly small.
correct me if i'm wrong, is my effort a step in the wrong direction?
Not necessarily. Education is worthwhile, and you'll probably learn
more about LDAP from exercises like this one. However, unless that's
the point of the exercise, then you're probably wasting time that you
could have spent solving more interesting problems.
11 messages in net.sourceforge.lists.courier-usersRe: [courier-users] courier-authlib-ldap
