experiment for setting up another port

Hi,

I am using XP and Apache version 2.0.46.

I am doing experiment by setting up the listening port as 8080 which was
done on the httpd.conf file. After I change the listening portion from
80 to 8080:-

.....
....
#Listen 12.34.56.78:8080
Listen 8080
.....
....
I then save the file as httpd8080.conf.

By then I go to DOS environment and type the following command in C:>

C:>apache -f C:>pogram files/apache group/apache2/conf/httpd8080.conf

and hit the <enter> key so as to start another server, but the computer
responds me that 'apache' is not an internal or external command.

Can anybody help me to solve this problem? what is going on?

By the way, before I do this small experiment, I use port 80 as the
listening port and type in the same statement in C:> except that the
last part is httpd.conf instead of httpd8080.conf, the same message also
appears?

What went wrong?

Regards
--
Direct access to this group with http://web2news.com
http://web2news.com/?comp.infosystem...ers.ms-windows
To contact in private, remove no-8sppam

Hi, Brian,

I just changed the Listen Directive to 8080 and I did not touch the
ServerName Directive. In that case, how to change the ServerName
Directive? Or what instruction I should put into that colmun?Please
advise.

Regards


Brian K. White wrote:
> Are you certain that your .conf for the alternate port is
> correct? Did you
> change both the Listen Directive and the ServerName
> directive? This message
> indicates that the second instance of Apache is still
> trying to bind to port
> 80.
>
> "bearbear" <dahung.news.invalid@web2news.net> wrote in message
> news:45697N561@web2news.com...
>> Dear Brian,
>>
>> I followed your suggestion, but the computer gave the following
>> message:-
>>
>> (OS 10048): make socks: could not bind to address
>> 0.0.0.80 no listening
>> sockets available, shutting down. Unable to open log.
>>
> etc..
>>> This just means that the Apache web server software is not
>>> in your system
>>> path (which it typically is not). Two solutions both
>>> simple. Do which ever
>>> one you prefer.
>>>
>>> Approach 1
>>> 1. Open Windows XP command prompt
> etc..
>>>> Hi,
>>>>
>>>> I am using XP and Apache version 2.0.46.
>>>>
>>>> I am doing experiment by setting up the listening port as
>>>> 8080 which was
>>>> done on the httpd.conf file. After I change the listening
>>>> portion from
>>>> 80 to 8080:-
>>>>
>>> etc..

--
Direct access to this group with http://web2news.com
http://web2news.com/?comp.infosystem...ers.ms-windows
To contact in private, remove noos5p+a3mm

Dear Brian,

In the file httpd8080.conf, I have made the following changes:-

.....
#Listen 12.34.56.78:8080
Listen 8080

.....

ServerName 127.0.0.1:8080

....

After I made the above changes and saved it. I then use IE, at the URL
I typed in http://127.0.0.1:8080. it shows it could not find the server
or DNS error.


In fact, I do not know what the outcome should be so as to demonstarte
port 8080 is on service. Or am I on the right track already?
What I should do next ?

Regards


---------------------
Brian K. White wrote:
> The listen directive should be
> Listen 8080
> The ServerName directive should be
> www.yourdnsname.com:8080
> or
> 12.34.56.78:8080 (if you only have an IP address)
>
> "bearbear" <dahung.news.invalid@web2news.net> wrote in message
> news:45818N524@web2news.com...
>> Hi, Brian,
>>
>> I just changed the Listen Directive to 8080 and I did
>> not touch the
>> ServerName Directive. In that case, how to change the ServerName
>> Directive? Or what instruction I should put into that colmun?Please
>> advise.
>>
>> Regards
>>
>> Brian K. White wrote:
>>> Are you certain that your .conf for the alternate port is
>>> correct? Did you
>>> change both the Listen Directive and the ServerName
>>> directive? This message
>>> indicates that the second instance of Apache is still
>>> trying to bind to port
>>> 80.
>>>
>>> "bearbear" <dahung.news.invalid@web2news.net> wrote in message
>>> news:45697N561@web2news.com...
>>>> Dear Brian,
>>>>
>>>> I followed your suggestion, but the computer gave the following
>>>> message:-
>>>>
>>>> (OS 10048): make socks: could not bind to address
>>>> 0.0.0.80 no listening
>>>> sockets available, shutting down. Unable to open log.
>>>>
>>> etc..
>>>>> This just means that the Apache web server software is not
>>>>> in your system
>>>>> path (which it typically is not). Two solutions both
>>>>> simple. Do which ever
>>>>> one you prefer.
>>>>>
>>>>> Approach 1
>>>>> 1. Open Windows XP command prompt
>>> etc..
>>>>>> Hi,
>>>>>>
>>>>>> I am using XP and Apache version 2.0.46.
>>>>>>
>>>>>> I am doing experiment by setting up the listening port as
>>>>>> 8080 which was
>>>>>> done on the httpd.conf file. After I change the listening
>>>>>> portion from
>>>>>> 80 to 8080:-
>>>>>>
>>>>> etc..

--
Direct access to this group with http://web2news.com
http://web2news.com/?comp.infosystem...ers.ms-windows