Well, I've recently decide to completly leave windows behind, so now I'm doing things to help expand my knowledge with linux, amongst other things.

I've just downloaded apache 2.0 and did the following commands.

#./configre
#make
#make install

That got it ready to go (I think so anyway)

The apache docs say to alter the httpd.conf file but I don't know anything about it, so if someone could help me out with things like, what to change...things like that.

Another thing, I tried the next step in the apache docs which is to run this command

#./apachectl start

And got this error in return...

Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs


If anyone could help me out with what I'm doing wrong, things I should do, things I should know, any advise really, It'd be greatly appreciated.

By the way, if anyone is wondering I'm using slackware 9.1 and 2.4.22 kernel.

Regards,
The_Messiah

~::BuMp::~

Someone...anyone...

Take a look at this guide.

You got that error because the socket is already in use. That means your apache tried to bind to port 80 and there was another application using it. Perhaps your distro came with a pre-installed http server...and that is more and more the norm so it doesn't surprise me that you get that error.

So far you are going in the right direction...trying to get started with Linux is perhaps the coolest IT experience that you'll ever have...even though it is full of these: ????

But the reward is well worth it!

Going back to your issue you can do 2 things:

1) Kill the process running on port 80 and start your web server again.

2) Make apache listen to another port, like 81 or 7777 or whatever you like....just remember any port under 1024 requires root privileges.

If you do start apache on port 81, remember that you will need to access it via your browser this way:

http://localhost:81

Cheers, and I hope this helped :-)

i have the same problem... apache isnt able to bind to port 80 and so it must be that another process is already listening there... how do I know what else could be doing that??! my distro must have come with a pre-installed http server right?

i am running ubuntu linux 4.10 (debian based) and have apache version 2.0.50 installed.

another note: if i access my webpage from within my internal private network, it works... but reports that it is apache 1.3 that is serving the file.

from the internet (external from my private network - which has appropriate port forwarding to allow HTTP requests) all I get is request timed out errors.

[EDIT]: aditional note: i tried to make apache2 listen to another port... changed port.conf to read "Listen 81" but still no response (request timed out) when accessing it from outside my private network.

I know that I have port forwarding activated and working because I can successfully ssh or ftp to my server...