the 'Macromedia command statements' one by one or something? Sorry but I need some v. basic
instructions!
Incidentally, I have spoken to Red Hat here in the UK about this issue this morning but it goes
beyond the normal level of their support. The engineer did say that he was 'surprised' that the
command for apxs didn't include a '-o' flag?! Don't know why that would be relevant but thought I
would pass it on!!
(I have tried several Google searches but am amazed that nobody else is having this problem? I am
happy to deploy the server using the standard connector - and trust Steven's experience of never
seeing a case of Apache crashing - but would feel much better if it was the proper connector!).
Many thanks, M
On 8/10/03, Steven Erat <[EMAIL PROTECTED]> wrote:
>Well, you're right that its better to recompile the connector for EAPI, although I've never seen an
actual case of Apache crashing due to this. I recommend finding the command that failed while
running apxs, then running that command from the same location by itself. Then you'd get an error
from the compiler instead of an apxs error code.
>
>-----Original Message-----
>From: Matthew Smith [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, October 08, 2003 6:30 PM
>To: CF-Linux
>Subject: RE: CFMX Connector Failure
>
>
>Hi Steven,
>
>I would like to use the pre-built connector but get the following error when starting Apache:
>
>Starting httpd: [Wed Oct 8 22:36:21 2003] [warn] Loaded DSO
>/opt/coldfusionmx/runtime/lib/wsconfig/1/mod_jrun.so uses plain Apache 1.3 API, this module might
>crash under EAPI! (please recompile it with -DEAPI)
>
>Am I missing something really obvious here? I must admit, I did think it odd that on a base RH
>install with standard RH RPMs that I needed to build a connector...
>
>What is the easiest way around this?
>
>Thanks,
>
>Matthew.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
