My apache children are seg faulting due to some combination of
DBI usage and the cookie-based authentication/authorization
scheme from chapter 6 in the "eagle" book by L. Stein and D.
MacEachern. I have read the ApacheDBI documentation, scoured
mailing lists, deja.com, etc., but I'm hoping someone might be
able illuminate what is going on here...
The authentication/authorization process is working smoothly.
Just after a ticketed client is revalidated (ie., just after
leaving Apache::TicketAccess with success), however, the apache
child seg faults. If I comment out all DBI references in the
Apache::Ticket* modules used for password querying, and just
hard-code a guaranteed password match, the seg fault disappears.
Without any authentication attempts at all, DBI works smoothly.
The db connection is done within each child upon the first db
query (NOT in the main process).
In looking over ApacheDBI, it's not clear it is doing anything
significantly different in terms of the timing of connections
among children.
Any clues?
Am I missing something special that ApacheDBI does that would
prevent this problem?
Cheers,
Ed Loehr
