Hi folk,
I have quite a number of trees set up ... accounts, people, hosts,
printers, mounts, etc etc etc. Right now they are all under one big
database, dc=ncsu,dc=edu in separate ou containers. Sometimes I find
myself wishing I had the ability to set things like...
on people I want the sizelimit to be 500
on printers I want no limit
on hosts I want sizelimit 1
... basically limits based off the trees.
To date I haven't found a way to do this and unless I'm mistaken, the
limits command is tied to a specific database. (different from the
sizelimit command which appears to be global)
So I have a two part question here.. first off, are there good pros
or serious cons to splitting up trees into multiple configured
databases? Is that a horrible terrible idea? If you search at the
root of dc=ncsu,dc=edu and ou=people,dc=ncsu,dc=edu is a separate
database, will the search carry over into ou=people?
Generally I'm just trying to think of things in a "could I be doing
this better" way at the moment. I mean tons of things use cn. Would
it be helpful if each tree had it's own index of cn instead of "one
big" cn index?
Likewise, is there any use of the limits command that I'm just not
aware of that lets you specific based off the search tree what the
limitations are?
Thanks for whatever thoughts y'all might have!
Daniel
---
You are currently subscribed to ldap@umich.edu as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
