Dear Alex,
The good news is that it bloats only on one server,
so the problem must on that configuration.
There were a couple of memory leaks reported for postgres 7.4,
not sure if these hit you (google around):
http://www.postgresql.org/docs/7.4/static/release-6-5.html
do you have a chance to
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
Hello Saurabh
Have you seen the version here? It already include nsoracle
http://www.friendlybits.com/en/inf_tec_en/win32openacs_en/
hope this helps
Brian
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf Of Saurabh
Sisodia
Sent: 03 March 2008 17:10
Hi Brian,
Thanks for the help, I think this should help though I need to check with the
client if he is OK with this version. I have somehow got the nsoracle built (it
needed nsdb.lib instead of some other library which was there). Though I think
this version would be a much better thing to
Hello Gustaf,
Thanks for the suggestions - I will try upgrading to Postgres 8.2.
As to the script, there was a problem with install-aol, and install
seem to work ok.
However I resolved that issue - will update the script.
Is there any good and clear documentation for the options available in
For those of you with project ideas, I think the best way forward is to
include them with the GSoC application that the Tcl community is putting
together. The relevant page is http://wiki.tcl.tk/20832
Matt
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply
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
16 matches
Mail list logo
