I have some questions about gcc optimization settings for AOLserver:
Is there any danger or drawback to compiling nsd8x and various
loadable modules with different -O settings? -O2?
What -O setting do most of you here use and recomend for gcc? Gcc
allows it, but is it particularly useful to
On Thu, Nov 21, 2002 at 01:53:17PM -0500, Dossy wrote:
On 2002.11.21, Andrew Piskorski [EMAIL PROTECTED] wrote:
Why didn't the mutex locking approach work?
Are you sure you're actually locking the /same/ mutex from both
pieces of code (reentrant.c and your wrapper around the vendor
Damn.
I think that you will run into problems with optimization unless you
use all the gcc options to tell it that statics are volatile. Most
compilers will assume that statics within a C function can only be
changed by that function, but that isn't true with multiple threads
executing the code.
We're
does anyone have any ns_socklistencallback sample code?
I posted a change yesterday to form.tcl, the purpose being to ensure
that temp files got deleted if the upload is aborted. But I goofed
and changed ns_atclose to unlink; not good.
Here is another diff. The idea is to unlink the main temp file right
after creating it, before ns_conncptofp has a
Here's a piece of test code I've used in
the past:
# This proc is run when a connection occurs
proc handle_socklistencallback {rfd wfd}
{ ns_log notice "A client has connected to the
socket" while {[set line [string trim [gets $rfd]]] != ""}
{ lappend headers
$line } ns_log notice "CLIENT
