After spending another night with it, I think it was a problem similar to http://groups.google.com/group/modwsgi/browse_thread/thread/1766eb9947f971b0/4ff3cf9a647de66d involving SELinux permissions on F13 rather than a symbol conflict.
Will see if I can replicate in rawhide and hope it isn't a running theme of tight SELinux policy producing segfaults. Aiden On Jan 25, 10:19 pm, Graham Dumpleton <[email protected]> wrote: > On 26 January 2011 00:50, aiden bell <[email protected]> wrote: > > > Hi all, > > > A while back I posted about libuuid symbol conflicts, and the > > resolution was to remove the offending > > Apache module. > > Can you remind me more about what the original problem was and what > two bits of software were using the conflicting symbol name? > > > I am however getting similar conflicts resulting in > > segfaults. > > > As a general question, is there a better solution than the removal of > > apache modules with conflicting symbols? > > Still using the single Apache installation, no. > > Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
