Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
OpenLDAP
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Christopher Ng
OpenLDAP
Commits
31f34d69
Commit
31f34d69
authored
21 years ago
by
Kurt Zeilenga
Browse files
Options
Downloads
Patches
Plain Diff
Misc Update
parent
35dc15ad
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
servers/slapd/slapi/TODO
+1
-4
1 addition, 4 deletions
servers/slapd/slapi/TODO
with
1 addition
and
4 deletions
servers/slapd/slapi/TODO
+
1
−
4
View file @
31f34d69
- de-IBM SLAPI
- add a config statement, or redefine the dynamic backend one,
"modulepath", to set/modify the load path also for plugins
(both plugins and modules use ltdl, so "modulepath" suffices ...)
...
...
@@ -6,11 +7,7 @@
- use syslog where available?
- add some plugin monitoring stuff in back-monitor (e.g. a subentry
for each plugin with data from struct Slapi_PluginDesc)
- This is a very tough task: try to implement a sandbox to execute
plugins in, trap deadly signals and possibly disable unsafe plugins
without crashing slapd (fork from inside thread? trap signals
and longjump to next plugin execution? Brrr).
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment