At 4:52 PM +0100 10/28/06, Nick Kew wrote:
On Sat, 2006-10-28 at 09:08 -0400, Daniel Griscom wrote:
>[Sat Oct 28 08:57:29 2006] [crit] (70023)This function has not been
>implemented on this platform: DBD: driver for [DBDriver unset] not
>available
>[Sat Oct 28 08:57:29 2006] [crit] (70023)This function has not been
>implemented on this platform: DBD: failed to initialise
You can ignore those messages if you don't want dbd.
Oh, I'd assumed these "[crit]" errors meant Apache hadn't even started up.
But the best solution if you have no need of an SQL backend
is just don't load mod_dbd in the first place.
Well, THAT worked. I just put a "#" in front of the line "LoadModule
dbd_module modules/mod_dbd.so", and the errors are gone. Most
excellent. (I'd thought that mod_dbd might be intertwined with the
abundance of other modules, but nope!)
Yes, it's a bug that you get those error messages when you
didn't think you had configured dbd at all.
I'll second that. Cryptic error messages emitted by code that
shouldn't even be executing.
Authentication is just one thing you do with dbd.
And it's way OTT to use an SQL backend for that,
if you don't have an SQL application somewhere too!
Well, I am using mySQL, but in the PHP-based MantisBT, so (I think)
Apache won't be involved.
Thanks for the help,
Dan
--
Daniel T. Griscom [EMAIL PROTECTED]
Suitable Systems http://www.suitable.com/
1 Centre Street, Suite 204 (781) 665-0053
Wakefield, MA 01880-2400
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
