Thank you very much for following up and the contribution. nsTimeLimit is indeed the user-level parameter to configure. there is a mention in this guide: https://docs.redhat.com/en/documentation/red_hat_directory_server/13/html/management_configuration_and_operations/searching-entries-and-tuning-searches#setting-user-and-global-resource-limits-by-using-the-command-line but this use case is different and interesting. We could add an Upstream HowTo/doc page about it, or even document this into one of the RHDS guides. Happy New Year! M.
On Wed, Dec 31, 2025 at 10:00 PM Bob Green via 389-users < [email protected]> wrote: > On Wed, Dec 31, 2025 at 12:27 PM Bob Green <[email protected]> > wrote: > > > > On Wed, Dec 24, 2025 at 10:39 AM Mark Reynolds <[email protected]> > wrote: > > > > > > Hey Bob, > > > > > > What you want is probably pointer COS: > > > > > > > https://docs.redhat.com/en/documentation/red_hat_directory_server/11/html-single/administration_guide/index#About_CoS-How_a_Pointer_CoS_Works > > > > > > The issue with this is it works for all entries under a subtree. There > > > is no filtering. So you can apply it to all users under > > > ou=people,dc=example,dc=com by creating the COS definition entry > > > directly under that branch. > > > > > > Not sure if this will work for you, but it's all we got at the moment. > > > > Thank you. I managed to get this to work once I realized that the > > nsSizeLimit and nsLookThroughLimit cosAttribute entries had to include > > operational in the cosPointerDefinition: > > > > cosAttribute: nsSizeLimit operational > > cosAttribute: nsLookThroughLimit operational > > > > I am now running into "Time limit exceeded (3)" when running a query > > that takes over 30 seconds. I was hoping adding nstimelimit: -1 to > > the COS template would overcome this limitation, but I have yet to get > > it to work. I've tried adjusting a variety of cn=config limit and > > time(out) attributes but to no avail. Can anyone please point me to > > whatever attribute needs adjusting? > > After rebuilding my instance I no longer see the time limit exceeded > warning. I believe the attribute to overcome the limit is indeed > nstimelimit, and can only account for it not working previously > possibly due to a configuration change I failed to keep track of. I > apologize to the list for the spam, and wish all a happy new year. > > Bob > -- > _______________________________________________ > 389-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >
-- _______________________________________________ 389-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
