Dear Iuri,
you are right, there is a problem with the sample config file for OpenACS,
which is included in the tar file used by install-ns.sh. If have updated
naviserver-4.99.18.tar.gz on sourceforge to include a fixed sample
config file.
You have three options:
a) specify in install-ns.sh for "version_ns" the value "HEAD" .
b) refetch the tar ball
c) add in the config file the ".so" extension (see below).
This is the traditional way of loading shared objects,
which works in all versions.
many thanks for reporting
-gn
Background:
The problem was that "nsproxy" (without extension) is a binary program,
and "nsproxy.so" is the shared libray. When "nsproxy" (without extension)
is used for the module in the config file, naviserver 4.99.18 tries to load
the binary program as shared object and fails. I have fixed this
issue actually already on the weekend in the NaviServer source code,
so if one installs from bitbucket, the issue should be gone.
+++ b/openacs-config.tcl Tue Mar 12 09:19:10 2019 +0100
@@ -693,7 +693,7 @@
ns_section ns/server/${server}/modules {
ns_param nslog ${bindir}/nslog
ns_param nsdb ${bindir}/nsdb
- ns_param nsproxy ${bindir}/nsproxy
+ ns_param nsproxy ${bindir}/nsproxy.so
#
# Load networking modules depending on existence of Tcl variables
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
