.
janine
On Mar 9, 2007, at 1:38 AM, Maurizio Martignano wrote:
Dear all,
I've got a question (possibly a newbie's one) on the memory
allocated by Aolserver (4.0.10) when running OpenACS (5.1.5).
When monitoring (with top or atop) the memory used by Aolserver running
Hello all.
I've included Titi's suggestion in the current version of the Win32-
OpenACS port. So now NSD is a well behaved windows service.
Thanks for your help,
Maurizio
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED]
with
Hello there,
Please have a look at the following Win32-OpenACS port:
http://www.friendlybits.com/en/inf_tec_en/win32openacs_en/
This port has been compiled using Visual Studio 2008 Professional Edition
and I believe you should be able to compile it also with the Express
Edition.
The
I just forgot to mention...
Compiling with Visual Studio 2008 is just as easy (or as difficult) as
compiling with gcc on a Linux/Unix box.
Cheers,
Maurizio
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf Of
Shedis
Sent: 26 April 2008 06:09
To:
Dear all,
When this community produces a new stable release of Aolserver, let
it be 4.5.1 or 4.5.x, I'll be more than happy to produce a new version of
the Win32-OpenACS distribution containing it.
Cheers and thanks,
Maurizio
-Original Message-
From: AOLserver Discussion
Dear all,
Sometime ago I made some tests on the memory leaks of
aolserver+tcs+openacs.
I'd like to share my two cents worth of what I believe I found, hoping it
might help.
Aolserver uses TCL, and TCL's got three different memory managers:
1. Standard: using the malloc, free, etc...
on memory usage
On 2008.05.01, Maurizio Martignano [EMAIL PROTECTED] wrote:
When using Zippy I noticed that the memory occupied by Aolserver (nsd)
always grows, without being released.
That's probably because we don't invoke madvise() anywhere. Of course,
apparently on MacOS X madvise
Dear Titi,
The proper version of the file, properly compiled and tested is the
one attached to this email message.
Hope it helps,
Maurizio
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf Of
Titi Alailima
Sent: 05 May 2008 19:03
To:
Hello Thomas,
the variable you seem to be missing
Tcl_HashTable NsOpenSSLServers;
is declared inside the file
sslcontext.c
From the errors you're getting I believe you have not included this file in
your build.
I'm currently working on providing my Win32-OpenACS
9446 Apr 13 2004 x509.c
-rw-r--r-- 1 root root5804 Jul 15 23:51 x509.o
-Prem Thomas
On Jul 16, 2009, at 8:54 AM, Maurizio Martignano wrote:
Hello Thomas,
the variable you seem to be missing
Tcl_HashTable NsOpenSSLServers;
is declared inside the file
sslcontext.c
From
Hello all,
I could try to add this module to my Win32-OpenACS distribution.
Anyhow I would just compile the module. I've no time to test its actual
behavior nor to properly support it.
It would be a take as is and compile thing.
Cheers,
Maurizio
-Original Message-
From: AOLserver
Dear Balaji,
Thanks a lot for your question.
I’m the maintainer of the “standard” OpenACS Windows (32) port.
http://www.spazioit.com/pages_en/sol_inf_en/win32-openacs_en/
First of all let me state that the Win32-OpenACS 1.19 installation procedure as
well as all its
/working on Windows 64 bit as such as a 64 bit binaries (as 64 bit
app). Running 32 bit binaries on 64 bit (WOW) is what we currently do, but
that is not good enough. Any idea if anyone including you have attempted such a
thing on AOL?
On 7/1/2010 12:43 PM, Maurizio Martignano wrote:
Dear Balaji
Dear all
I’m the maintainer of the Windows Port of OpenACS and ]project-open[.
All my installers contain a working version of Aolserver 4.5.1, including
the the Oracle driver, which has been compiled with Visual Studio 2010.
Of course, all the installers contain also the source code (and the used
Dear all,
I'm the maintainer of the Windows Port of OpenACS.
Recently (22/07/2011) I got the CVS HEAD version of Aolserver and compiled
it with Microsoft Visual Studio 10 for Windows 32 bit and Windows 64 bit.
I did this because I wanted to take profit of the mods
Hello all,
Some few clarifications, I am afraid I wasn't clear.
The compilation in itself was rather simple and went almost ok.
The issue was in the behavior in the testing
Some of the code, eg, function calls to the networking parts and so on, are
working in the tar ball
by #ifdef __WIN32__ as needed,
etc.
On 8/3/11 1:19 PM, Maurizio Martignano wrote:
By looking at the code I have the feeling that the interest in
supporting Windows is fading down.
[...]
Any opinion?
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply
Dear all,
Id like to provide you with very few examples to explain
what I was talking about:
These problems manifested themselves in the Win64 version
driver.c
void
NsWaitDriversShutdown(Ns_Time *toPtr)
{
Driver *drvPtr = firstDrvPtr;
int status = NS_OK;
@LISTSERV.AOL.COM] On Behalf Of
Don Baccus
Sent: 04 August 2011 14:53
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Aolserver Progress - Some few examples
On Aug 4, 2011, at 12:24 AM, Maurizio Martignano wrote:
inttrigger[2]; /* Wakeup trigger pipe. */ ß Why
] as (int) is the problem --
Windows might complain about some signed/unsigned thing at compile time, but
in both cases, (int) is 32 bits.
On 8/4/11 3:24 AM, Maurizio Martignano wrote:
inttrigger[2]; /* Wakeup trigger pipe. */ ß Why is
this an int when it was a SOCKET (any
, Maurizio Martignano wrote:
It is not a matter of understanding
It is a matter of testing
On Windows 64 int trigger[2] doesn't work whereas SOCKET trigger[2] does
work.
On top of that in several other places SOCKET has been used, so if for no
other reason, I suggest one of the code maintainers
@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Aolserver Progress - Some few examples
On Aug 4, 2011, at 7:20 AM, Maurizio Martignano wrote:
5. I have to disagree with your statement A Unix pipe is just a pair
of file descriptors, and a file descriptor in Unix is just an
integer.
Feel free
[mailto:AOLSERVER@LISTSERV.AOL.COM] On Behalf Of
Don Baccus
Sent: 04 August 2011 19:25
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Aolserver Progress - Some few examples
On Aug 4, 2011, at 9:55 AM, Maurizio Martignano wrote:
All of this depends on the week type system of C, were types
) is the
problem
-- Windows might complain about some signed/unsigned thing at compile
time, but in both cases, (int) is 32 bits.
On 8/4/11 3:24 AM, Maurizio Martignano wrote:
int trigger[2]; /* Wakeup trigger pipe. */ ß Why is this an int when
it was a SOCKET (any justification
:26 PM, Maurizio Martignano wrote:
Don
In Aolserver source code
95% of more of the times sockets are declared as SOCKET; the other
times as int.
This is an inconsistency and is a fact.
If you wanted to develop only for Unix why did you use SOCKET in some
occasions and int in some
Subject: Re: [AOLSERVER] Aolserver Progress - Some few examples
On Aug 4, 2011, at 11:26 AM, Maurizio Martignano wrote:
If you wanted to develop only for Unix why did you use SOCKET in some
occasions and int in some others?
Damnit, that was never the point.
You said that you thought
see this in the
oversight of SOCKET for the driver trigger we've been talking about and the
NsMap code not yet implemented for Windows. I agree a scan of all SOCKETs
not being declared are SOCKET's makes good sense.
-Jim
On Aug 4, 2011, at 8:28 AM, Maurizio Martignano wrote
[mailto:neum...@wu-wien.ac.at]
Sent: 05 August 2011 14:23
To: AOLserver Discussion
Cc: Maurizio Martignano
Subject: Re: [AOLSERVER] Aolserver Progress - Some few examples
Dear Maurizio and all...
i have updated cvs on sourceforge with most of your patches. A few points
are questionable (see
2011 15:52
To: Maurizio Martignano
Cc: 'AOLserver Discussion'
Subject: Re: [AOLSERVER] Aolserver Progress - Some few examples
Dear Maurizio,
i guess, everything is fine with you with the head version on sourceforge.
For me, it is still unclear, why 4.5.1 worked for you, but not the head
tough to maintain.
-Jim
On Aug 3, 2011, at 1:54 PM, Maurizio Martignano wrote:
Hi Jim,
Once again I'll take ]project-open[ as example.
Please look in here:
http://sourceforge.net/projects/project-open/files/project-open/V3.5/
How big is the Windows Installer (which installs on both
. The difference
is like between a graceful and an ungraceful shutdown.
-gustaf
On 05.08.11 16:29, Maurizio Martignano wrote:
Dear Gustav,
I understand your concerns about Tcl_Finalize. but it is
called just when the process/service is about to end.
Once it ends the OS takes charges
are right,
that the memory leak does not matter due to the shutdown. The difference
is like between a graceful and an ungraceful shutdown.
-gustaf
On 05.08.11 16:29, Maurizio Martignano wrote:
Dear Gustav,
I understand your concerns about Tcl_Finalize. but it is
called just when
Tcl_Finalize() is not run, the registered exit handlers are not
executed. How serious this is depends on the exit handlers. You are right,
that the memory leak does not matter due to the shutdown. The difference
is like between a graceful and an ungraceful shutdown.
-gustaf
On 05.08.11 16:29, Maurizio
does work, it should
absolutely be done.
On 8/6/11 9:35 AM, Maurizio Martignano wrote:
Dear Gustav (and all the others)
I did some digging.
And here are the results..
1. Tcl_Finalize gets properly called in Windows 64 by tclsh (ok
tlcsh85t.exe) at exit time
2. From within Aolserver
();
#endif // !_WIN64
But, on all other platforms where invoking Tcl_Finalize does work, it should
absolutely be done.
On 8/6/11 9:35 AM, Maurizio Martignano wrote:
Dear Gustav (and all the others)
I did some digging.
And here are the results..
1. Tcl_Finalize gets properly called
://msdn.microsoft.com/en-us/library/ms682583.aspx
On 06.08.11 16:28, Maurizio Martignano wrote:
It is me again
Well I noticed that the change I suggested about Tcl_Finalize did not make
it into CVS HEAD.
If it doesnt go there, I am afraid I will have to anyhow introduce it
myself in my
@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Aolserver Progress - Some few examples All's
well that ends well
On 07.08.11 17:37, Maurizio Martignano wrote:
Dear Gustav,
Thank you.
Alls well that ends well
Im not sure all the changes I suggested are still in the codebase
37 matches
Mail list logo
