k...@redshift.com wrote:
>> k...@redshift.com wrote:
>>> I installed Apache as a service as normal, then tried to run it. It
>>> ran...but it won't read the httpd.conf file. Even changing the
>>> service to call httpd.exe -k runservice -f (path to conf file) *does
>>> not work*. I can only run h
Damon,
UAC is likely to revert changes to config files, yes, without warning.
Evil it is.
Frank
k...@redshift.com wrote:
Well, I solved it even though I have no idea what was going on. After
disabling UAC, I happened to glance at the httpd.conf again and it was
back to the default. I edited
Well, I solved it even though I have no idea what was going on. After
disabling UAC, I happened to glance at the httpd.conf again and it was
back to the default. I edited it AGAIN to set the correct configuration
and lo and behold, now I can run httpd as a service.
Did UAC do that?
If it did, i
> k...@redshift.com wrote:
>> I installed Apache as a service as normal, then tried to run it. It
>> ran...but it won't read the httpd.conf file. Even changing the
>> service to call httpd.exe -k runservice -f (path to conf file) *does
>> not work*. I can only run httpd manually, from the comman
k...@redshift.com wrote:
> I installed Apache as a service as normal, then tried to run it. It
> ran...but it won't read the httpd.conf file. Even changing the service to
> call httpd.exe -k runservice -f (path to conf file) *does not work*. I
> can only run httpd manually, from the command prom
I installed Apache as a service as normal, then tried to run it. It
ran...but it won't read the httpd.conf file. Even changing the service to
call httpd.exe -k runservice -f (path to conf file) *does not work*. I
can only run httpd manually, from the command prompt, with the -f
parameter, and ge
