Excellent, everything is working fine now.
A big thank you to everybody who helped.
A special thank you to Juan, Gustaf and Tom.
Cheers guys, this won't be the last time I ask for help thought :)
On 05/03/2008, Tom Jackson [EMAIL PROTECTED] wrote:
On Wednesday 05 March 2008 13:31, Xavier
One more note on this,
The patch:
http://aolserver.cvs.sourceforge.net/aolserver/aolserver/nsd/pools.c?r1=1.11r2=1.12
Even though you get an error here, it appears that the data still takes
effect. The reason is that the tests are done against the stored values.
Nothing is done to fix the
Dossy Shiobara schrieb:
On 2008.03.04, Michael Andrews [EMAIL PROTECTED] wrote:
OK - I'll take a look tonight. I think that a 0 as the threadtimeout
value use to mean no timeout. I guess I'll need to look at the C to
see what the changes were.
Is this file even needed anymore?
OK, guys, I owe you an apology.
The server is working fine, the reason I thought that it was not
working is that in the base.tcl file the server address is 127.0.0.1,
but in fact when the server starts, it says: Notice: nssock: listening
on 127.0.1.1:8001
Now I tried to connect to 127.0.0.1 and
Ok, I have set timeout to be 1 and now I don see the error anymore.
Unfortunatelly, I still can connect to the server.
I have tried to connect to 8000 to no avail.
this si my config file:
set home [file dirname [ns_info config]]
set pageRoot $home/servers/server1/pages
ns_section ns/parameters
Hello Xavier,
I have the following lines in my server config file:
set httpport 8003
set hostname [ns_info hostname]
set address127.0.0.1
ns_section ns/server/${servername}/module/nssock
ns_param port$httpport
ns_param hostname
On Wednesday 05 March 2008 13:31, Xavier Bourguignon wrote:
OK, guys, I owe you an apology.
The server is working fine, the reason I thought that it was not
working is that in the base.tcl file the server address is 127.0.0.1,
but in fact when the server starts, it says: Notice: nssock:
Hello Gustaf,
yes I compiled tcl8.4.18 myself with --enable-threads.
I will redo everything and see what happens, will keep you guys posted on this.
Thank you
On 04/03/2008, Gustaf Neumann [EMAIL PROTECTED] wrote:
Dear Xavier,
There is a known problem with Tcl_GetMemoryInfo() in
Tcl 8.5
Xavier Bourguignon schrieb:
Hello Gustaf,
yes I compiled tcl8.4.18 myself with --enable-threads.
I will redo everything and see what happens, will keep you guys posted on this.
what do you get when doing a
nm /home/xbourgui/programs/tcl8.4//lib/libtcl8.4.so | fgrep Tcl_GetMemory
?
You
allright,
I have followed the directions on how to install aolserver from there:
http://alex-andr.org/notes/tiki-index.php?page=nsd+setup+script
I have run the script, and it seems that everything is ok now in terms
of make and make install.
Now I have another problem.
I start aolserver with
On 2008.03.04, Xavier Bourguignon [EMAIL PROTECTED] wrote:
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: nscp:
listening on 127.0.0.1:8001
[04/Mar/2008:18:26:09][25063.3074169744][-nssock:driver-] Notice:
nssock: listening on 127.0.1.1:8000
It seems that there is a problem with
I think that file does not do good validation on the config settings
before it uses them. I'll fix that. In the mean time, set the timeout
param in the config to a number or remove it all together.
M
On Mar 4, 2008, at 2:08 PM, Xavier Bourguignon wrote:
allright,
I have followed the
This is due to a change for the pools setup code.
I think Gustaf made changes to the defaults in the C code. Probably the
pools.tcl file needs to reflect the changes to the C code? I noticed the
changes, but I don't use that version of the pools code.
Looking at $home/modules/tcl/pools.tcl
Tom Jackson schrieb:
Gustaf, is the intent just to flag potentially dangerous values?
yes
--
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
OK - I'll take a look tonight. I think that a 0 as the threadtimeout
value use to mean no timeout. I guess I'll need to look at the C to
see what the changes were.
Is this file even needed anymore?
On Mar 4, 2008, at 2:37 PM, Tom Jackson wrote:
This is due to a change for the pools setup
On 2008.03.04, Michael Andrews [EMAIL PROTECTED] wrote:
OK - I'll take a look tonight. I think that a 0 as the threadtimeout
value use to mean no timeout. I guess I'll need to look at the C to
see what the changes were.
Is this file even needed anymore?
IMHO, the semantics around
On Tuesday 04 March 2008 13:15, Michael Andrews wrote:
OK - I'll take a look tonight. I think that a 0 as the threadtimeout
value use to mean no timeout. I guess I'll need to look at the C to
see what the changes were.
I think that a zero did mean no timeout, did that change too?
Is this
I think there is only one default pool - that all servers use.
The pools.tcl code simply sets the default pool's values to what was
in the config. I know the config params are in a server-specific
section, and maybe that should be changed, or a default pool per
server should be created by
I ran make clean, then make all and I got this on make all:
gcc -O2 -Wall -Wno-implicit-int -fno-strict-aliasing -fPIC -O2
-fno-strict-aliasing -pipe -nostartfiles
-I/home/xbourgui/Desktop/aolserver-4.5.0/include
-I/home/xbourgui/programs/tcl8.4//include -DNO_CONST
-DHAVE_LIMITS_H=1
Dear Xavier,
There is a known problem with Tcl_GetMemoryInfo() in
Tcl 8.5 (see e.g.
http://aspn.activestate.com/ASPN/Mail/Message/tcl-core/3610677
or
http://sourceforge.net/tracker/index.php?func=detailaid=1868171group_id=10894atid=110894).
however, since you are using tcl 8.5, this seems
20 matches
Mail list logo
