Well 'httpd' is now up n running. The solution was simple and found at:
http://www.gidforums.com/t-1889.html
I changed the port that 'httpd' was listening on from '80' to '78'. What gave me the clue as to where to look was the error msg:
(98)Address already in use:make_sock:could not bind to address[::]:80
(98)Address already in use:make_sock:could not bind to address[0.0.0.0]:80
I googled the second string and found the above website. I changed ports and ran:
[root@localhost ~]# httpd -k start
Now I need to figure out who is hogging port 80.
Well I discovered that 'httpd.conf ' and 'system-config-httpd.conf ' do not play well together.
'http.conf ' has a listen line:
#Listen 12.34.56.78:80
Listen *:80
and
'system-config-httpd.conf ' also has a listen line:
#Listen 12.34.56.78:80
#Listen *:80
I discovered that on my system both can not be 'listening'. If they are 'httpd' won't start or re-start. It has to be one or the other. As you'll notice I commented out 'Listen *.:80' in 'system-config-httpd.conf '. Also, using 'System, Administration, Server Settings, HTTPD' GUI causes the line in '/ect/httpd/conf.d/system-config-httpd.conf ' to be uncommented and you'll have to open it with a text editor as root and re-comment it.
But my headache is only partially cured. I can access my 'web server' page and 'ftp' dir from my LAN WinXP box using a 192.168.0.xxx IP but not a 74.229.248.xxx IP. Others located in Virginia can. Grrrrrr! Router issue? New one installed (VersaLink C90-327W30-06) or possibly SELinux issue.
phil