Message-ID: <1100D69203AAD2118E3C00508B8B9E8A1709A2@INTECH002> From: "Heupink, Mourik Jan C." Date: Sun, 26 Nov 2000 13:44:07 +0100 Subject: RE: [SLE] Apache compiling - --prefix=/usr/sbin does not work - h ow to get apache working when compiling yourself yep: that exactly the problem i've been having. i wonder why suse put's apache in a different location. This why, you have to edit the scripts to get the self-compiled apache going with suse. But anyway: glad to hear that i'm not overlooking something, or missing something really obvious. mourik jan <p>-----Original Message----- From: zentara [mailto:zentara@gypsyfarm.com] Sent: Saturday, 25 November, 2000 20:17 To: Heupink, Mourik Jan C. Subject: Re: [SLE] Apache compiling - --prefix=/usr/sbin does not work - how to get apache working when compiling yourself <p>"Heupink, Mourik Jan C." wrote:

Hi.

Thanks!

Just checked their homepage, looks very promising!

Your welcome. I compiled apache alot, and what happens is it installs itself in /usr/local/apache/bin and you need to use the command "apachectl" to start it. It is hard to get suse's startup script to start it. I have run both versions at once. I use "rcapache start" to start the suse version; and then "apachectl start" to start the self compiled version. Good luck.