.
Another thing that might be useful is a mem free check.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
On Thu, Aug 26, 2004 at 12:29:46PM -0700, Aaron Bannert wrote:
+1 (seems to work fine on Solaris 9/x86)
Success on solaris sparc 8 too with the small detail that I had
to disable ipv6 to avoid a segfault in the tcp test.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
/~pquerna/dev/apr-1.1.0-rc1/
Please Test help test!
Tests out nicely on SuSE SLES8 - All tests passed. for both apr and
apr-util.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
, then it is just because there
is no announce for 1.1.0 yet.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
contain both underlying database error codes, a standardized
APR error code, etc.
Something like that would certainly be preferable - in the general case
standard error messages might be fine, but we'd be missing a lot
of useful info if there was no way to access the raw error.
vh
Mads Toftum
dir -
http://svn.apache.org/viewcvs.cgi/apr/apr/trunk/test/
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
On Thu, Nov 24, 2005 at 01:13:03PM +, Gerry wrote:
Is anyone actively working on documenting APR ?
I can see nothing about any such activity on the website.
There's an external tutorial at http://dev.ariel-networks.com/apr/
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water
from me too - the current behavior of being
forced to either install apr first or getting stuck with the system apr
has already bitten me more than once.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
candidate for inclusion in a future update.
+1 from the peanut gallery - this would indeed be very practical.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
running memcached instance.
Indeed - requiring everyone to test everything is pointless.
I wonder if it would make sense for a future version of the tests in
apr/apr-util to include a summary of what was tested making it easier
to post results?
vh
Mads Toftum
--
`Darn it, who spiked my coffee
.
By that reasoning, all ldap auth and mod_dbd should also be vetoed...
and how about all dbm (except sdbm) - or have you already implemented
minimal oracle, postgres and ldap servers in apr-util test/ ? And how
about the distcache interface hacked directly into mod_ssl?
vh
Mads Toftum
--
`Darn
for [EMAIL PROTECTED])
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
then integrate the code into better/simpler usage models.
+1 from the peanut gallery - got to get started somewhere.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake
failure:s3_pkt.c:1052:SSL alert number 40
23457:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake
failure:s23_lib.c:226:
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
be different and not all applicable across all implementations.
Works for me.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
defined within seems like a sensible plan.
Probably the first place one would look, so that makes perfect sense to
me.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
.
If you keep aiming for the lowest common feature set, it is going to end
up making the SSL support in apr a lot less useful.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
at making this a reality.
Thoughts?
I like the idea very much as it would make it simpler to extend apr with
support for other convenience libraries.
vh
Mads Toftum
--
http://soulfood.dk
- perhaps abstracting away some of the more unpleasant bits
of the openssl api.
vh
Mads Toftum
--
http://soulfood.dk
make it to the public through
the minutes from the board meeting. Having it on the apr site before
that would be nice.
vh
Mads Toftum
--
http://soulfood.dk
As if the 'sendfile' 'hangs' until that happens.
I think that's all of it.
vh
Mads Toftum
--
http://soulfood.dk
e headers and
> the code itself.
>
There's a 30 page chapter on APR in Nick Kew's The Apache Modules Book.
vh
Mads Toftum
--
http://flickr.com/photos/q42/
22 matches
Mail list logo