On Fri, 2004-01-30 at 20:04, Stas Bekman wrote:
Aha. So it's not direct SDBM_File. Can you first test with SDBM_File itself,
so that we may be can point the fat finger at MLDBM::Sync?
It's not MLDBM::Sync. I get the exact same results when using
SDBM_File. Also, the error is thrown when
On Fri, 2004-01-30 at 19:52, Ged Haywood wrote:
Another one: is mod_ssl involved anywhere?
It is.
From mod_ssl-2.8.16-1.3.29/INSTALL
NOTE: The --enable-rule=SSL_SDBM option enabled the use of the
built-in SDBM library instead of a custom defined or vendor
supplied DBM library.
Hi Perrin,
On 1 Feb 2004, Perrin Harkins wrote:
On Fri, 2004-01-30 at 19:52, Ged Haywood wrote:
Another one: is mod_ssl involved anywhere?
It is.
NOTE: The --enable-rule=SSL_SDBM option
As far as I can tell from httpd -V, that option was not used ...
I may end up just writing some
Has anyone ever had trouble with SDBM_File not being able to open dbm
files created under mod_perl from a command line script? I noticed that
apache 1.x seems to include an sdbm library, and I wonder if that is
being used by mod_perl, making the dbm file it writes incompatible with
the sdbm
Hi Perrin,
On Fri, 30 Jan 2004, Perrin Harkins wrote:
Has anyone ever had trouble with SDBM_File not being able to open dbm
files created under mod_perl from a command line script?
Stupid question: this isn't the old first 4k not getting flushed
file locking bug?
73
Ged.
--
Reporting
On Fri, 2004-01-30 at 18:59, Ged Haywood wrote:
Stupid question: this isn't the old first 4k not getting flushed
file locking bug?
I don't see how it could be. The mod_perl code unties the file after
using it.
The message I get is panic: sv_setpvn called with negative strlen and
it doesn't
Hi guys,
On Fri, 30 Jan 2004, Stas Bekman wrote:
I think perl brings in its own SDBM implementation
Another one: is mod_ssl involved anywhere?
From mod_ssl-2.8.16-1.3.29/INSTALL
NOTE: The --enable-rule=SSL_SDBM option enabled the use of the
built-in SDBM library instead of a custom
Perrin Harkins wrote:
On Fri, 2004-01-30 at 19:45, Stas Bekman wrote:
I'm not familiar with SDBM guts, but it could be that mod_perl and perl have a
different idea about some data type used by SDBM. like 32/64 bits so LFS could
be an issue. Are you sure it's the same perl?
At first I thought
