Hi, Derek, All
Mystery solved - as usual, it was something really simple
It turned out that I was taking some of the binary libraries from old
4.0.10 installation instead of new 4.5 .
To make it more messy, some of libs like nspostgres.so still work just
fine from the old installation, so presumably nssock.so or/and
nslog.so were responsible for the bad effect.
It's quite quirky however, that nsd was able to start with those wrong
libs, and I saw no suspicious messages in the log.
Tom pointed to a method of getting the *actual* nsd configuration, and
it helped, because the wrong locations became immediately obvious.
(as opposed to the original config.tcl where paths are taken/hidden by
variables).
I am attaching this piece of ADP page here, may be it will be helpful
to someone else as well.
Thanks,
~ Alex.
#---------------- adp page which shows the actual nsd config ---------------
<%
set sections [ns_configsections]
# in order to sort by ns_set name
foreach section $sections {
set section_names([ns_set name $section]) $section
}
foreach name [lsort [array names section_names]] {
set section $section_names($name)
ns_adp_puts "<div style='font-weight:bold; border:1px solid green;'>\
ns_section $name\
</div>"
set i [ns_set size $section]
while {[incr i -1] >= 0} {
ns_adp_puts "<li>[list ns_param [ns_set key $section $i] \
[ns_set value $section $i]]"
}
}
%>
#---------------------------------------------------------------------
On 2/19/07, derek <[EMAIL PROTECTED]> wrote:
Can you post your nsd.tcl?
On Feb 19, 2007, at 5:19 PM, Alex wrote:
> Any ideas on this topic?
>
> Thanks,
> ~ Alex.
>
> On 2/17/07, Alex <[EMAIL PROTECTED]> wrote:
>> On the same note,
>>
>> It does not seem to be a namespace issue, in both cases (loading
>> libraries and adp page code) namespace is global (::).
>>
>> Also, I captured all available commands in :: namespace at the
>> time of
>> aolserver initialization and loading libraries. Then I compared them
>> to the commands available for adp code.
>>
>> As we already know, all commands/procs learned from libraries at
>> startup time are not available. But what was even more quirky,
>> some of
>> _ns procs are not available for adp either.
>> for example,
>> _ns_http_gets _ns_http_puts _ns_http_read _ns_http_readable
>> _ns_isaolpress
>> ns_cleanup ns_cleanupchans ns_cleanupvars ns_cookiecharset
>> ns_dbquotename
>> ns_dbquotevalue ns_encodingfortype ns_eval ns_findset
>> ns_formfieldcharset
>> ns_formvalueput ns_getchannels ns_getform ns_getformfile
>> ns_htmlselect
>> ns_httpget
>> ns_httpopen ns_httppost ns_init ns_isformcached ns_issmallint
>> ns_localsqltimestamp
>> etc.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
