Where does it say that? httpd uses it extensively, so if it's not, I'd
tend to think we'd have noticed by now...
--Cliff
On Thu, 8 Jan 2004, Donald Doane wrote:
> Okay, will do that, but it's called in
> "flood_easy_reports::easy_process_stats()" and it seems APR
> documentation implies it is
The following comment is from apr_lib.h:
* apr_vformatter does not call out to any other code, it is entirely
* self-contained. This allows the callers to do things which are
* otherwise "unsafe". For example, apr_psprintf uses the "scratch"
* space at the unallocated end of a block, and doesn't
On Thu, 8 Jan 2004, Donald Doane wrote:
> The following comment is from apr_lib.h:
>
> * apr_vformatter does not call out to any other code, it is entirely
> * self-contained. This allows the callers to do things which are
> * otherwise "unsafe". For example, apr_psprintf uses the "scratch"
>
On Fri, 2004-01-09 at 04:50, Cliff Woolley wrote:
[...]
> That seems to say to me that apr_psprintf is in fact threadsafe after all.
> :-)
It actually depends on how apr_psprintf is called, pass it the same pool
in two concurrent threads and it might blow up. Is the apr_psprintf
function otherwi
Thank you for the claification.
Sander Striker wrote:
On Fri, 2004-01-09 at 04:50, Cliff Woolley wrote:
[...]
That seems to say to me that apr_psprintf is in fact threadsafe after all.
:-)
It actually depends on how apr_psprintf is called, pass it the same pool
in two concurrent threads and
Joshua Schnee wrote:
I am attempting to set up the latest Apache server and RHEL 64bit to use
in a Specweb99 run and am running into cgi issues. I am very new to
Apache, and am having difficulty getting apache to run/use/find my
cgi-script. Static content works fine, but I am getting improper
> the various types of URLs. Fortunately, the client prints the URLs before it
> tests them. Cut-n-paste the failing URLs into a browser navigation bar and
> hit
> enter. What does the browser display?
Even better, the manager script dumps the result of its tests to files with
names like 'dync
On Thu, Jan 08, 2004 at 12:57:43PM -0800, Stas Bekman wrote:
> It's really hard to guess what did you do. As suggested below if you could
> create a sample package which reproduces the problem, upload it somewhere
> and post the URL here, we could be much more helpful. You should be able to
> cr
>>
>> $ perl Makefile.PL MP_APXS=/apache/2.1/prefork/perl-5.8.2/bin/apxs
>> ...
>> Configuring Apache/2.1.0-dev mod_perl/1.99_13-dev Perl/v5.8.2
>>
>> $ make && make test
>> ...
>> using Apache/2.0.49-dev (prefork MPM)
>>
>> waiting 120 seconds for server to start: .httpd: module "mod_perl.c"
>> i
Geoffrey Young wrote:
$ perl Makefile.PL MP_APXS=/apache/2.1/prefork/perl-5.8.2/bin/apxs
...
Configuring Apache/2.1.0-dev mod_perl/1.99_13-dev Perl/v5.8.2
$ make && make test
...
using Apache/2.0.49-dev (prefork MPM)
waiting 120 seconds for server to start: .httpd: module "mod_perl.c"
is not
compat
William McKee wrote:
[...]
I've been calling it as `perl -d t/TEST`. I have tried calling it using
`t/TEST -debug perl` but the debugger hangs or, more recently, I get the
message '!!! server is not ready yet, try again.' Running the tests
without debugging or with the gdb debugger works fine. I ne
11 matches
Mail list logo