On Sunday 16 May 2004 01:08 am, Paul Tammes wrote:
Suse calls the apache config file for apache 2 httpd2.conf iirc.. And stores it in /etc/system/config/suseconfig/YaST/ or something similar unlogical
locate httpd2.conf locate httpd.conf /etc/apache2/httpd.conf
Presumably setup.pl tries to modify httpd.conf in another location and complains (and rightfully so).
So I should find the path setup.pl is using to httpd.conf and change it to /etc/apache2/httpd.conf?
I remember looking foor the httpdconfig files a while before finding them. Try apache2 status or something like that on the commandline if all else fails. (Other guess: Setup changed apache 1 configs, and Suse starts apace 2 or vice versa)
Is apache2 running at all? SuSe defaults to NOT run a webserver iirc. This is quite safe and OK for most users, untill you want to run SQL-Ledger
Yes it is running.
In that case, apache2 start or httpd2 start should do the trick..