On 16 Nov 2010, at 18:15, Tom Jackson wrote:
http://aolserver.git.sourceforge.net/git/gitweb-index.cgi
I am not sure why you think using gitweb is good - I find it pretty unpleasant.
More to the point is that any clone has a full revision history so I am not
sure why you would really care so
You should use the version from sourceforge.
http://sourceforge.net/project/showfiles.php?group_id=3152package_id=41577
--
Jeff Davis http://xarg.net mailto:[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED
for us since we do things like load
all the test procs and create procs only used at install time etc.
And I would really like to get it working.
--
Jeff Davis http://xarg.net mailto:[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email
On Fri, 14 Jan 2005 10:38:46 -0500, Dossy Shiobara [EMAIL PROTECTED]
said:
Dossy Using PostgreSQL? Could there be a memory leak in the nspostgres
Dossy driver? I'd defer to the OpenACS folks to say whether there are any
Dossy known memory leaks in any of the OpenACS Tcl code.
I did a
If try to use nsreturn [ns_gzip ...] the special handling for
encodings won't be done correctly (that's my guess anyway, not having
looked at the code). You really need to do all the encoding jive
before compressing.
--Jeff
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this
).
--Jeff
--
Jeff Davis http://xarg.net mailto:[EMAIL PROTECTED]
--
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.
Tcl_UtfToExternalDString
simply makes a second copy of the string without changing it. It
seems to me it should skip the Tcl_UtfToExternalDString altogether if
the output encoding is utf-8 (and it's really only a couple line
change to do so).
--
Jeff Davis http://xarg.net mailto:[EMAIL PROTECTED
work with aolserver 3 though.
--
Jeff Davis http://xarg.net
--
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.
dossy I'm currently working off the aolserver_v40_bp branch source (which is
dossy currently 4.0.3).
Could we get a 4.0.3 src tarball up on Sourceforge. For gentoo (and
fink I think) it is much easier to create build scripts if the tarball
is there and properly named.
The current one is
case since freenode
already has #openacs and #tcl (and a number of other FOSS projects I
like to keep up with). I probably would not participate on a regular
basis if it was not on irc.
--
Jeff Davis http://xarg.net mailto:[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove
);
if (s != NULL) {
reqPtr-length = atoi(s);
if (reqPtr-length 0
reqPtr-length sockPtr-drvPtr-servPtr-limits.maxpost) {
return SOCK_ERROR;
}
}
} else { ...
--
Jeff Davis http
AOLServer 4 + nspostgres, nsoracle, nscache and nsxml from sourceforge
all work fine with OpenACS 4.6. OpenACS 4.7 (cvs HEAD) needs some of the
i18n tcl API from the ad13 patches.
I. To remove yourself from this list:
Send a message to [EMAIL PROTECTED] with the following text in
the BODY of
Andrew, I have built nsoracle on 4.0 several times without a problem.
I can fix the line endings but to be honest it hasn't been a problem
for me either when editing the file or build the module.
I have installed openacs under postgres and oracle without a problem
as well so nspostgres, nsoracle,
I have installed OpenACS with AOLServer 4.0beta1 and it all seems to
work well. The only remaining issue I see is that when I kill the
server it hangs at the check for event threads and never actually
dies. It does not happen with 3.3+ad13 or 3.5.2 on the same server
(well the same once nsdb.so
Nathan, I will check it out in the debugger. I tried to reproduce it just
now, but after running for a few minutes (and a couple sceduled procs) it
did not hang on shutdown. I will let it run for a while and see
if it happens again (it had happened the last several times I restarted
though). In
Well, waiting a while made it unstoppable...
One thing that I noticed was this -sched:idle0- thread which was not there
at the start and only showed up later.
name parenttid flags ctime proc arg
-conn:oatest4::0 -driver- 41010 Mon, 27 Jan 2003
16 matches
Mail list logo
