1 Mar
2006
1 Mar
'06
21:41
On Wednesday 01 March 2006 13:31, Istvan Gabor wrote:
I even don't think anymore that this is an apache problem. I think this is a suse/YAST specific configuration issue.
OK, some random 'forensics/troubleshooting' notes: a. Is there anything else running, like Skype, using the port and interface you're trying to configure? This has been known to interfere with Apache2, both starting *and* installation... check with netstat: netstat -tulpen | grep ":80" b. Verify/adjust your host settings in: 1. YaST Control Center => Network Services => Host Names 2. YaST Control Center => Network Services => DNS and Host Name It can't hurt to keep "poking at" this problem until something informative crops up, right? regards, Carl