:
field of your email blank.
--
Nathan Folkman
[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
can let go and quickly move on. (p. 70)
--
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.
--
Nathan
On 8/9/07, John Buckman [EMAIL PROTECTED] wrote:
On Aug 9, 2007, at 2:07 AM, Nathan Folkman wrote:
A variant is used in production, although it's not exactly the same.
Can you say more about variant?
The biggest difference is that the version in Google Code includes support
for using HTTP
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list
, Nathan Folkman [EMAIL PROTECTED] wrote:
It hasn't been officially released or announced as of yet. Tt's in
more of an initial development release phase at the moment. Still lots of
documentation to be done. There is currently no roadmap or timeline to share
with everyone either at this time
in the email message. You can leave the
Subject: field of your email blank.
--
Nathan Folkman
[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
to
the shared memory pool, which can have the net effect of lowering the
overall process size.
- n
On 8/7/07, Daniël Mantione [EMAIL PROTECTED] wrote:
Op Tue, 7 Aug 2007, schreef Nathan Folkman:
You might also want to try running AOLserver without the Tcl threaded
allocator (Zippy). You
in the email message. You can leave the
Subject: field of your email blank.
--
Nathan Folkman
[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
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list
/
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from
of your email blank.
--
Nathan Folkman
[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.
the
Subject: field of your email blank.
--
Nathan Folkman
[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
and
couldn't find any mention of the new setup (until someone pointed it
out) but plenty of talk about the old ones. I think it's in the
release notes, but nobody reads those ;^)
- Ian
On 7/30/07, Jeff Rogers [EMAIL PROTECTED] wrote:
Nathan Folkman wrote:
Those parameters moved and are now
ns_param threadtimeout 120
ns_param map GET /
ns_param map POST /
tom jackson
On Thursday 26 July 2007 08:53, Nathan Folkman wrote:
You'd actually want to do it by adding the following to the end of your
configuration file:
ns_pools set procsmsgmgr
PROTECTED] with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED]
with the
body
, at 10:29 AM, Nathan Folkman wrote:
You are absolutely correct. Lack of documentation continues to be
one of the biggest issues with this project in my opinion. Not sure
how best to resolve this at this point to be completely honest.
Would be a great start if other folks would start
of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
--
Nathan Folkman
[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
- 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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com
I think we did actually talk about some of the stuff that was coming down
the pipe when we used to have those AOLserver chats. Not sure what happened
to those. I personally haven't been officially assigned to AOLserver
support for a while now.
- n
On 8/1/07, Nathan Folkman [EMAIL PROTECTED
. You can leave the
Subject: field of your email blank.
--
Nathan Folkman
[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
that
it executes at the correct time. When is this time anyway? Apparently it
is
not during the sourcing of the config file.
tom jackson
On Wednesday 01 August 2007 09:33, Nathan Folkman wrote:
As I said before, if you have issues with the changes made in 4.5,
simply do not upgrade. There were
$poolName [ns_info server] $poolMethod
$poolPattern
ns_log Notice ns_pools registered $poolName [ns_info
server] $poolMethod $poolPattern
}
}
}
}
-
tom jackson
On Wednesday 01 August 2007 10:50, Nathan Folkman wrote:
Bingo
Probably would be that difficult, although honestly not a priority for
anyone here. Have at it! ;)
- n
On 7/30/07, Jeff Rogers [EMAIL PROTECTED] wrote:
Nathan Folkman wrote:
Those parameters moved and are now controlled via the ns_pools Tcl
command:
This issue keeps coming up. How hard
of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
--
Nathan Folkman
[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
] wrote:
Its 4.5.0
On 7/26/07, Nathan Folkman [EMAIL PROTECTED] wrote:
What version of AOLserver are you running?
On 7/26/07, Shedi Shedi [EMAIL PROTECTED] wrote:
Hi
Patform: suse 10.1 (2.6.16.21-0.25-default)
I have configured my nsd config.tcl as below:
ns_param
maxdropped 0
ns_param maxthreads 20
ns_param minthreads 10
ns_param threadtimeout60
Can you tell if my configuration is correct?
regards,
On 7/26/07, Nathan Folkman [EMAIL PROTECTED] wrote:
Those parameters moved and are now controlled via the ns_pools Tcl
command
of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
--
Nathan Folkman
[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
email blank.
--
Nathan Folkman
[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.
/
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from
://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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list
PROTECTED]
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED]
with the
body
.
--
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http
.
-john
--
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver
AOLSERVER in the email message. You can leave the
Subject: field of your email blank.
--
Nathan Folkman
[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
]
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
--
Nathan Folkman
[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
it
does not work?
Cheers
Agnieszka Kukalowicz
--
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.
--
Nathan Folkman
, 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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email
if this was for tdom or tclxml.
-J
--
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.
--
Nathan Folkman
[EMAIL
benefit, being able to use the same code
in
all threads would be very nice.
tom jackson
On Wednesday 28 February 2007 11:41, Nathan Folkman wrote:
Don't you open yourself up for a race condition if that code is in a
scheduled proc?
--
AOLserver - http://www.aolserver.com/
To Remove yourself from
Cool.
BTW, I wouldn't call this a leak, and would instead call it misuse of tDOM.
;-)
On 2/28/07, Jeff Rogers [EMAIL PROTECTED] wrote:
Nathan Folkman wrote:
Don't you open yourself up for a race condition if that code is in a
scheduled proc?
If it was an aolserver scheduled proc then yes
AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
--
Nathan Folkman
[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
PROTECTED] with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject:
field of your email blank.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED]
with the
body
in the email message. You can leave the
Subject: field of your email blank.
--
Nathan Folkman
[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
: field of your email blank.
--
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.
--
Nathan Folkman
[EMAIL PROTECTED
/
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from
in the email message. You can leave the
Subject: field of your email blank.
--
Nathan Folkman
[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
in the email message. You can leave the Subject:
field of your email blank.
--
Nathan Folkman
[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
] with the
body of SIGNOFF AOLSERVER in the email message. You can leave the
Subject: field of your email blank.
--
Nathan Folkman
[EMAIL PROTECTED]
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL
fix really need to get into the
code.
--
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.
--
Nathan Folkman
[EMAIL
-
*From:* AOLserver Discussion [mailto:[EMAIL PROTECTED] *On
Behalf Of *Nathan Folkman
*Sent:* Wednesday, December 13, 2006 8:07 PM
*To:* AOLSERVER@LISTSERV.AOL.COM
*Subject:* Re: [AOLSERVER] tcmalloc
Exactly right. Thanks for jogging my memory! ;-) Here's a snippet from one
of our custom build scripts
need to
mention aolserver location in anyway .
*
and finally LD_PRELOAD tcmalloc at AOLserver startup time. This will
override malloc() and free(). *
How do i do that ?
Nathan Folkman wrote:
Basically what you need to do is compile Tcl so that it doesn't use the
threaded allocator, and instead
\
cat tclConfig.sh | sed -e 's/-DUSE_THREAD_ALLOC=1//' tclConfig.sh.new \
cp Makefile.new Makefile \
cp tclConfig.sh.new tclConfig.sh
On 12/13/06, Jeff Rogers [EMAIL PROTECTED] wrote:
Nathan Folkman wrote:
What you need to do is build a version of Tcl that has support for
threads
... Anyone got any ideas? Seems like
the two things we'd want to compare are performance and overall memory
usage.
--
Nathan Folkman
[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
, aT [EMAIL PROTECTED] wrote:
Nathan Folkman wrote:
Anyone tried Google's tcmalloc with AOLserver instead of using Tcl's
threaded allocator? Looks like folks are seeing some good things with it.
http://dammit.lt/2006/12/06/google-perftools-tcmalloc-squid/
--
Nathan Folkman
[EMAIL PROTECTED
blank.
--
Nathan Folkman
[EMAIL PROTECTED]
Anyone tried Google's tcmalloc with AOLserver instead of using Tcl's
threaded allocator? Looks like folks are seeing some good things with it.
http://dammit.lt/2006/12/06/google-perftools-tcmalloc-squid/
--
Nathan Folkman
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove
test
--
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.
[EMAIL PROTECTED] wrote:
Hi,
If memory serves, the zippy2 work was done against AOLserver 4.5,
which
uses slightly different semantics for building. I think you should be
able to simply change that line to be:
Makefile:41: [.]/aolserver/include/Makefile.module
Try the following as a replacement for the current Makefile:
CLEAN = clean-it
INSTALL = install-it
LIB = zippy2
LIBOBJS = tclThreadAlloc.o
CFLAGS += -I$(TCL)/generic
include $(AOLSERVER)/include/Makefile.module
$(LIB): $(OBJS)
$(LDLIB) $(LDFLAGS) -o $(LIB) $(LIBOBJS)
$(CLEAN):
[EMAIL PROTECTED] wrote:
Hi,
I have problem compiling zippy2 allocator.
I hoped to make some tests to compare Zippy2 with Hoard allocator,
but when I tried to build zippy2 I get errors:
Makefile:41: […]/aolserver/include/ns.mak: No such file or directory
I think it is due to missing ns.mak
[EMAIL PROTECTED] wrote:
I have some data urlencoded by JavaScript's escape function which is
turning a Unicode apostrophe into %u2019. AOLserver doesn't recognize
this. I can certainly fix this in specific locations, but to handle
this universally it seems it this would need to be be fixed
to take that on right now. So I am asking if
anyone had that in mind to do it. If not, it could eventually prove to be a
high enough priority for us as we move to more AJAX input, so we would revisit
allocating some resources to it at that point.
-T.
-Original Message-
From: Nathan
[EMAIL PROTECTED] wrote:
Is there anybody on this mailing list
If I get in troubles, I’m afraid the other zones on the mainframe
crashes as well as mine J
I’ll give a shot anyway. That the beauty of an attitude behavior!!!
I just need to do backups before
Best,
iuri
[EMAIL PROTECTED] wrote:
Has anyone been able to compile the nsmysql driver on os x tiger
10.4.8 / aolserver 4.5 / mysql 5? I've tried on intel and ppc,
neither work.
The result of make is as follows:
gcc -pipe -I/usr/local/mysql/include -Os -Wall -Wno-implicit-int
-fno-strict-aliasing
[EMAIL PROTECTED] wrote:
Following up on Stuart's call for clarification, can someone please send
some out some documentation, or point us to it, where we can figure out how
to use the new ns_limits/ns_pools functionality in 4.5.
We just used 4.5 in production and aolserver was limited to 100
[EMAIL PROTECTED] wrote:
This morning my server complained:
unable to alloc 2169111 bytes
How large was the nsd process when it crashed?
and thus exited. So, I'm thinking that malloc fragmentation may very
well be the problem.
I read recently that the
connsperthread
parameter no longer
[EMAIL PROTECTED] wrote:
So did setting connsperthread take care of the bloating? I keep
seeing assertions that memory use by AOLserver should level off at
some steady state - perhaps controlled by this parameter. But I have
yet to see any one come back and say I changed X to Y and now my
[EMAIL PROTECTED] wrote:
On 9/12/06, Nathan Folkman [EMAIL PROTECTED] wrote:
They are still supported. The base.tcl was supposed to be a simpler
and more bare bones configuration example. The plan was to add other
smaller configuration examples, such as the nscp.tcl which could then
be combined
The segfault is obviously a bug... I think what's being referring to is
the behavior that allows code to continue executing after an
ns_returnredirect unless an ns_adp_abort is explicitly specified.
- n
[EMAIL PROTECTED] wrote:
And the segfaulting when you do this? Also a feature? I'd call
[EMAIL PROTECTED] wrote:
(Apologies for the long email ahead ... but, I think it's worth a quick
read.)
On 2006.09.05, Rick Gutleber [EMAIL PROTECTED] wrote:
Support for more popular languages (come on, let's say it together, I
know it's hard, but Tcl is not popular) is probably the most
[EMAIL PROTECTED] wrote:
On 5 Sep 2006, at 17:57, Titi Ala'ilima wrote:
1) AOLserver probably needs a new name. Something that uses the NS
initials would be ideal so that all those ns_* commands actually make
sense again. Could we resurrect the NaviServer name?
Already taken! (OpenSource
An alternate strategy to exec'ing is to instead expose the low-level
C/C++ APIs as Tcl commands. If the code in question isn't thread safe,
you can create a library that you would load from the nsproxy, which if
you remember, is basically just a single-threaded tclsh that is fork'd
and exec'd
Couple of general things about the Tcl threaded memory allocator (zippy)
that might help better explain what you are seeing...
- The Tcl memory allocator is a x2 allocator optimized for lock
avoidance between threads. This results in very high performance, but
comes at the cost of almost x3
Just saw this on Digg - pretty hip!
http://www.cit.gu.edu.au/~anthony/graphics/imagick6/
- n
[EMAIL PROTECTED] wrote:
An alternate strategy to exec'ing is to instead expose the low-level
C/C++ APIs as Tcl commands. If the code in question isn't thread safe,
you can create a library that you
[EMAIL PROTECTED] wrote:
On Tuesday 29 August 2006 20:29, Jeff Hobbs wrote:
You are correct that the main problem is in trying to fork when not
closely followed by exec*().
But with Tcl exec, you never call fork, screw around and then call exec*(), do
you? Is this an issue for C
[EMAIL PROTECTED] wrote:
On Aug 30, 2006, at 8:56 AM, Nathan Folkman wrote:
What is it you are trying to exec?
From OpenACS we mostly just exec Imagemagick. I can't think of
anything else.
janine
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send
[EMAIL PROTECTED] wrote:
On Wednesday 30 August 2006 10:32, Nathan Folkman wrote:
[EMAIL PROTECTED] wrote:
On Aug 30, 2006, at 8:56 AM, Nathan Folkman wrote:
What is it you are trying to exec?
From OpenACS we mostly just exec Imagemagick. I can't think
[EMAIL PROTECTED] wrote:
On Aug 30, 2006, at 10:32 AM, Nathan Folkman wrote:
So the easy way to do this would be to exec from the nsproxy. Better
option might be to wrap the C API, although I'm not entirely sure
whether or not Imagemagick is truly thread-safe. Even if it is not,
you'd
[EMAIL PROTECTED] wrote:
On Saturday 19 August 2006 21:07, Tom Jackson wrote:
On Saturday 19 August 2006 19:12, Hossein Sharifi wrote:
(although I do plan to fix the
incorrect usage of exec as well)
So I've never heard that you can't use exec from AOLserver. How is this
[EMAIL PROTECTED] wrote:
Hi!
I'm trying to use the throttle xotcl package with AOLServer 4.5, which works
in 4.0.10. When I call a page, I get the error
invalid command name ::xotcl::Object
from the
ns_register_filter postauth GET * throttle
page filter.
The xotcl namespace is
Locks are not shared with the nsd process. The libnsd library came about as a result of folks wanting some of the AOLserver core Tcl APIs from within stand alone tclsh processes.
You might also want to look at the new nsproxy module. That code allows you to start a pool of tclsh processes that
Have you looked at the "ns_schedule_proc" APIs?
Example:
http://panoptic.com/wiki/aolserver/Ns_schedule_daily
- n
-Original Message-
From: [EMAIL PROTECTED]
To: AOLSERVER@LISTSERV.AOL.COM
Sent: Tue, 15 Aug 2006 6:48 PM
Subject: [AOLSERVER] cron (ie, timed) jobs in aolserver
The plan was to roll all that back so we could get to a simple, and some
would argue, more standard build style:
- autoconf
- configure
- make
Not quite there yet though it seems... In the mean time, the README file
is accurate, and contains instructions that illustrate how things differ
Try the following steps (if you haven't already) from the aolserver
directory, and see if this works for you:
1. ./configure --with-tcl=/usr/local/tcl/lib
--prefix=/usr/local/aolserver --enable-symbols
2. /usr/local/tcl/bin/tclsh8.4 nsconfig.tcl -install
/usr/local/aolserver -debug
3. make
If you haven't already, would you mind filing this as a bug against 4.5
over at SourceForge? I set up a new category for 4.5 bugs. I'll try to
take a look one of these evenings. Also, please provide a fail case. Thanks!
- n
[EMAIL PROTECTED] wrote:
Now... if I visit a bogus url, I *still*
The latest Tcl version (8.4.13) works great! Haven't spent any amount of
time testing with upcoming Tcl 8.5, but it also should work fine I believe.
Not sure exactly what memory issues you are referring to, but if you are
building Tcl multi-threaded, then you are using the threaded allocator
version of Tcl.
Is it fair to assume that those memory usage problems have been
eliminated in AOLserver 4.5.0 when used with Tcl 8.4.1.3?
Thanks.
Harvey Lunenfeld
Internet Corporation
[EMAIL PROTECTED]
- Original Message - From: Nathan Folkman [EMAIL PROTECTED]
To: AOLSERVER
How are you building Tcl and AOLserver?
- n
[EMAIL PROTECTED] wrote:
Oh boy, another OS X build problem from me... :(
-
ranlib: can't open file:
/Users/bas/dev/aolserver-4.5.0/lib/libnsthread.a (No such file or
directory)
make[1]: *** [install-dll] Error 1
make: ***
In terms of distributed key/value pair data structures, there are two
additional methods we've used here at AOL:
* AV (auto variables)
* NV (network variables)
AV's are a read-only data structure that under the covers is built on a
sorted list for quick access, and small size. The files get
Speaking of SOB, we're working on getting the code to our dci (Digital
City) module ready for release to the Open source community. This
module contains the following items which folks may find interesting:
* SOB - Dossy described this below. Basically it's what we use at AOL to
forward cache
] wrote:
On Monday 26 June 2006 21:47, Nathan Folkman wrote:
Yes. In fact, there's a new nszlib AOLserver module as part of the
AOLserver 4.5 release.
Thanks !!! Can it also be used on/in Aolserver 4.0.10
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list
Yes. In fact, there's a new nszlib AOLserver module as part of the
AOLserver 4.5 release. Here's the relevant release notes:
nszlib:
The popular nszlib module written by Vlad Seryakov has been
integrated into the core release with modifications to
enable the new Ns_Gzip
? Thanks!
- n
[EMAIL PROTECTED] wrote:
It doesn't compile on 32 bit FC5 as several posts have showed. It is a
problem with tcl and threads. I use gentoo, but have 1 FC5 box so I am
no Fedora expert.
Nathan Folkman wrote:
I know it compiles on 32-bit FC5. Haven't tried on 64-bit FC5.
- n
[EMAIL PROTECTED] wrote:
On 2006.06.20, Eduardo Perez [EMAIL PROTECTED] wrote:
I would like to know if aolserver continues to be maintained or if you
are considering it deprecated and suggest people to move to other
server.
I am asking because I see no new releases and the
On the heels of the Zippy2 code release, I've also committed a new
module called nsloopctl. This module redefines Tcl's for, foreach,
and while commands to allow
both the gathering of statistics about each loop, and also to provide a
mechanism to pause, cancel, and resume a particular loop.
the tcl commands. At some point a tcl error isn't appended
to the result, but I don't know if this is your code of copied from tcl.
How is it possible to pause/resume a loop?
tom jackson
On Monday 05 June 2006 06:20, Nathan Folkman wrote:
On the heels of the Zippy2 code release, I've also
then us! ;-)
- n
tom jackson
On Monday 05 June 2006 08:11, Nathan Folkman wrote:
In AOLserver 4.5 the following new Tcl APIs are provided:
ns_for
ns_foreach
ns_while
ns_loop_ctl
The usage is exactly the same as the nsloopctl module I checked in,
and which I documented
PM, Nathan Folkman wrote:
Check out, or update, your code from the HEAD.
- n
[EMAIL PROTECTED] wrote:
Hi,
Thank again for your help. How could I get this fix ? Is it working ?
Herick
On Jun 2, 2006, at 3:58 PM, Jim Davidson wrote:
I just checked in the fix which is really just to disable
1 - 100 of 328 matches
Mail list logo
