Argh! Just WORK Apache!!

[Dre'qo]

I'm about to buy a PC just for Windows NT and IIS! HELP!

I'm fairly a newbie when it comes to Linux/UNIX and completely a newbie setting up Apache. My ultimate goal is to get MySQL running and some sort of ASP module.

I probably should have just left the built in version of Apache but I couldn't find the config file. I searched everywhere. Everyone I talked to said it was the httpd.conf file but it was no-where to be found! I got to looking around on the net and downloaded iTools from Tenon which claims that it "simplifies Apache configuration & maintenance" It ended up not working for me so I successfully removed it from the system (I think).

I finally decided to be bold and compile apache 1.3.19 (remember I'm a newbie, thats a pretty bold move!) I used instructions on Stepwise and it installed without trouble... I even have a .conf file now! However from now on apache won't start up.

[www:/Users] root# httpd -v
Server version: Apache/1.3.19 (Darwin)
Server built: 04/04/01 17:24:17
[www:/Users] root# apachectl start
/usr/sbin/apachectl start: httpd could not be started
[www:/Users] root# httpd start
Bus error

BTW... whats with all these different commands? httpd? apachectl?

Any tips? I really don't want to have to end up with a Windows server. HELP!

- Dre'qo -

 

[marmoset]

BTW... whats with all these different commands? httpd? apachectl?

apachectl is simply a script that starts and stops or restarts the Apache
daemon, based on the parameters you run it with. It's just there
because it's easier than messing around with PIDs and kill
and HUPs and stuff...

httpd is the actual main apache executable. Apache started
it's life a long time ago in a galaxy far far away as
a (big) set of patches to NCSA's http daemon. "A Patchy
web server", get it?

 

[Dre'qo]

Thx. So to start apache manually I'd in most cases use apacheclt. I found myself yet in another problem... for whatever the reason apache isn't giving me any errors in the error log. It has before and I tried clearing out the file so I could clearly see the errors being returned for my specific problem. Seems like ever since it hasn't placed anything in the error log. (I really need to stop trying to change everything! heh)

Maybe I'm just not getting any errors? eek. Could I maybe step up the log level to like 'debug' or something in the .conf file? It would really help if I knew a bit more of whats going on instead of just the "httpd could not be started".
<blockquote><code># If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "/private/var/log/httpd/error_log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn</code></blockquote>
- Dre'qo -