Different distros are slightly different, but generally there is a central apache conf file that also loads sub-files.
The sub-files will be loaded with an Include directove in the main file, so if you cannot find the servername entry in the main file, grep it for Include statements, then grep the Included files for the setting. If you still can't find it, conclude that your distro didn't bother to set it. That may be because your distro expects you to set up your machine so that it knows its own FQDN, which often isn't the case on small private LANs. If it assists, here is the comment to ServerName on my gentoo box: # # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If this is not set to valid DNS name for your host, server-generated # redirections will not work. See also the UseCanonicalName directive. # # If your host doesn't have a registered DNS name, enter its IP address here. # You will have to access it by its address anyway, and this will make # redirections work in a sensible way. # On Fri, May 18, 2007 12:41 pm, Matthew Whiting wrote: > yep, that did the trick, thanks. there wasn't already a servername > directive in httpd.conf so I was just wondering if it was supposed to be > set elsewhere. its been a while since I last setup apache2 in ubuntu > with virtual hosts, etc. would have thought you'd set the directive in > the default file under sites enabled, but that didn't work.. >>> apache2: Could not reliably determine the server's fully qualified >>> domain name, using 127.0.1.1 for ServerName >>> >>> Googled for help, but haven't been able to come up with the answer yet. >>> Doesn't seem to be hindering anything.. I'm only going to be using >>> localhost for now. >> >> Perhaps you should set the 'ServerName' directive in >> /etc/apache/httpd.conf to an appropriate value. >> >> cheers, >> rohit. >> > > -- Nick Rout
