In a message dated 1/19/03 12:14:50 PM, [EMAIL PROTECTED] writes:


Is this expected behaviour - or od I maybe have config problem or something?

First, make sure you've got the latest head version of the 4.0 code. I fixed a bug in aolserver/bin/init.tcl a couple of days ago which was preventing any Tcl other then what was in aolserver/modules/tcl from being loaded.

Next, make sure you have the following configuration for each directory of Tcl files you'd like to source at startup.

ns_section "ns/server/${serverName}/modules"
ns_param yourDirectory tcl

If you want to source Tcl from directories outside of aolserver/modules/tcl, you'll need to also add the following to define your own private Tcl directory:

ns_section "ns/server/${serverName}/tcl"
ns_param library $home/servers/${serverName}/modules/tcl

- Nathan

Reply via email to