issue with db_module_dir parameter

Will Fiveash William.Fiveash at
Sat May 13 23:33:29 EDT 2006

On Sat, May 13, 2006 at 05:26:56PM -0400, Jeffrey Hutzelman wrote:
> On Friday, May 12, 2006 09:06:17 PM -0500 Will Fiveash 
> <William.Fiveash at> wrote:
> >On Thu, May 11, 2006 at 09:18:54PM -0400, Sam Hartman wrote:
> >>>>>>> "Will" == Will Fiveash <William.Fiveash at> writes:
> >>
> >>    Will> So what is the plan for how db_module_dir and dbname will
> >>    Will> work?
> >>
> >>    Will> Is db_module_dir going to be supported in a [dbmodules]
> >>    Will> entry or will dbname be given a absolute path to the plugin
> >>    Will> in order to load a plugin from a non-default plugin dir?
> >>
> >>Under typical usage, the compiled in default of db_module_dir will be
> >>used and a dbname like db2 or ldap will be given.
> >>
> >>db_module_dir will definitely be supported.
> >
> >Both globally and in specific [dbmodules] entries?
> >Currently it doesn't appear to work in specific [dbmodules] entries.
> It's not intended to; it's not a module-specific parameter.  The purpose of 
> this parameter is to control where the plugin system looks for modules. 
> That's a global setting, not a per-module one, just like the search 
> directories for PAM modules or NSS modules or SASL plugins or whatever.

Then I think it is important that the dbname parameter support absolute

Will Fiveash
Sun Microsystems Inc.
Austin, TX, USA (TZ=CST6CDT)

More information about the krbdev mailing list