Alex,
Might be something simple. What if the URL was /test instead of /test/ ?
Also, maybe define and register the proc with full namespace qualification:
::myproc ...
Otherwise, I haven't run into any issues with ns_register_proc in the new
release.
Where exactly is this file located? Maybe there is something with virtual
servers?
tom jackson
On Thursday 15 February 2007 22:10, Alex wrote:
> Hi,
>
> I am having strange problem wile moving 4.0.10 -> 4.5, CVS version
> 2006-12-15 ...
> it seemingly doesn't see procs defined in the library and registered
> with ns_register_proc.
>
> So this example code:
>
> #--- file test.tcl -will be picked up from lib directory ---
>
> ns_log debug "Loading test.tcl"
>
> proc reg_test {args} {
> ns_log debug "Ok, here"
> }
>
> ns_register_proc GET "/test/" reg_test
>
> ns_log debug "Loaded tsl.test - and proc [info procs reg_test] is defined"
>
> #---------------------------------------------------------
>
> gives Tcl exceptions when page http://192.168.1.1/test/ is requested:
>
> [16/Feb/2007:00:51:59][22157.3083470528][-main-] Notice: nsmain:
> AOLserver/4.5.0 starting
> ...
> [16/Feb/2007:00:52:00][22157.3083470528][-main-] Debug: Loading test.tcl
> [16/Feb/2007:00:52:00][22157.3083470528][-main-] Debug: Loaded
> tsl.test - and proc reg_test is defined
> [16/Feb/2007:00:52:00][22157.3083470528][-main-] Notice: nsmain:
> AOLserver/4.5.0 running
> [16/Feb/2007:00:52:00][22157.3083470528][-main-] Notice: nsmain:
> security info: uid=1005, euid=1005, gid=1005, egid=1005
> [16/Feb/2007:00:52:00][22157.3071925168][-sched-] Notice: sched: starting
> [16/Feb/2007:00:52:00][22157.3083470528][-main-] Notice: driver:
> starting: nssock
> [16/Feb/2007:00:52:00][22157.3067521968][-nssock:driver-] Notice:
> starting
> [16/Feb/2007:00:52:00][22157.3067521968][-nssock:driver-] Notice:
> nssock: listening on 192.168.1.1:80
> [16/Feb/2007:00:52:07][22157.3066465200][-conn:0-] Error: Tcl exception:
> invalid command name "reg_test"
> while executing
> "reg_test {}"
>
> Any quick ideas why that could happen?
>
> Thanks,
> ~ Alex.
>
>
> --
> 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.
