> On 24.06.2025, at 22:21, Georg Lehner <jorge...@magma-soft.at> wrote: > What is needed is a configuration option for the LDAP version to use, so that > one can adapt to the capabilities of the given server. > I do not see this as urgent. LDAPv3 was defined in RFC2251 (Dec 97) and is supported by OpenLDAP since 25 years (full compliance in 2000). the nsldap module uses ldap_sasl_bind_s(), which was not supported by v2, so, without v3 there is not much the module can do.
>>> Global Initialzation of a Tcl Module >>> > As I understand it, with the provided nsd-config.tcl the global libraries are > served from /usr/local/ns/tcl, as well as the private libraries for the > server default. > > I created a module as a subdirectory of /usr/local/ns/tcl and put an > initialization proc into my module into the file init.tcl and also execute it > within this file. When I load the module globally, the initialization proc > is not run and the module is not loaded. When I load the module in the > default server it is loaded/executed as expected. > > Code within /usr/local/ns/tcl/init.tcl is executed, but I do not want to > touch this file, since it is part of the installation of Naviserver. > I think the code works as designed. If you load the module globally, then the global library files are used. If you load the module per server, then the per-server library files are used. Do you say, this is not the case? If so, this is a bug. Do you expect that a globally loaded module uses the per-server library files? All the best -g
_______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
